Apparatus for transmitting broadcast signals, apparatus for receiving broadcast signals, method for transmitting broadcast signals and method for receiving broadcast signals

ABSTRACT

A method of receiving broadcast signals is provided. The method includes receiving the broadcast signals and decoding a service layer table including bootstrap information from the received broadcast signals. The bootstrap information indicates an MPEG Media Transport Protocol (MMTP) session carrying service layer signaling. The method further includes decoding the service layer signaling from MPEG Media Transport (MMT) packets based on the MMTP and decoding a transport session description from a Real-Time Object Delivery over Unidirectional Transport (ROUTE) session. In addition, service components are delivered by the MMT packets based on MPEG Media Transport Protocol, and non-real time components are delivered by Layered Coding Transport (LCT) packets in the ROUTE session. The service components delivered in the MMT packets and the non-real time components delivered in the LCT packets are decoded, respectively.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. application Ser. No.15/077,655, filed on Mar. 22, 2016, which claims priority under 35U.S.C. § 119(e) to U.S. Provisional Application No. 62/136,637, filed onMar. 23, 2015, and 62/144,311, filed on Apr. 7, 2015, all of which arehereby incorporated by reference as if fully set forth herein.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention relates to an apparatus for transmitting broadcastsignals, an apparatus for receiving broadcast signals, a method oftransmitting broadcast signals, and a method of receiving broadcastsignals.

Discussion of the Related Art

As analog broadcast signal transmission comes to an end, varioustechnologies for transmitting/receiving digital broadcast signals havebeen developed. A digital broadcast signal may include a larger amountof video/audio data than an analog broadcast signal and further includevarious types of additional data in addition to the video/audio data.

SUMMARY OF THE INVENTION

Accordingly, the present invention is directed to an apparatus forproviding a broadcast service at transmitting side and receiving sidefor future broadcast services and methods for providing a broadcastservice at transmitting side and receiving side for future broadcastservices.

That is, a digital broadcast system can provide high definition (HD)images, multi-channel audio and various additional services. However,data transmission efficiency for transmission of large amounts of data,robustness of transmission/reception networks and network flexibility inconsideration of mobile reception equipment need to be improved fordigital broadcast.

According to an object of the present invention, as included herein andbriefly described, the present invention proposes a system foreffectively supporting a next-generation broadcast service in anenvironment that supports next-generation hybrid broadcast using aterrestrial broadcast network and an Internet protocol (IP) network, anda related signaling scheme.

The present invention proposes a method of efficiently providing hybridbroadcast using both a broadcast network and an IP network.

The present invention proposes a method of providing application-basedenhancement based on an application for a basic broadcast service.

The present invention proposes a method of providing application-basedenhancement in synchronization with a broadcast service.

The present invention proposes architecture according to variousprotocols between a primary device (PD) and a companion device (CD), anda communication scheme between applications.

The present invention proposes architecture and a signaling scheme foreffectively delivering information about an electronic service guide(ESG), an emergency alert system (EAS), etc. from a PD side to a CDside.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention, illustrate embodiments of the inventionand together with the description serve to explain the principle of theinvention.

FIG. 1 illustrates a receiver protocol stack according to an embodimentof the present invention.

FIG. 2 illustrates a relation between the SLT and SLS according to anembodiment of the present invention.

FIG. 3 illustrates an SLT according to an embodiment of the presentinvention.

FIG. 4 illustrates SLS bootstrapping and a service discovery processaccording to an embodiment of the present invention.

FIG. 5 illustrates a USBD fragment for ROUTE/DASH according to anembodiment of the present invention.

FIG. 6 illustrates an S-TSID fragment for ROUTE/DASH according to anembodiment of the present invention.

FIG. 7 illustrates a USBD/USD fragment for MMT according to anembodiment of the present invention.

FIG. 8 illustrates a link layer protocol architecture according to anembodiment of the present invention.

FIG. 9 illustrates a structure of a base header of a link layer packetaccording to an embodiment of the present invention. Hereinafter, thestructure of the header will be described.

FIG. 10 illustrates a structure of an additional header of a link layerpacket according to an embodiment of the present invention.

FIG. 11 illustrates a structure of an additional header of a link layerpacket according to another embodiment of the present invention.

FIG. 12 illustrates a header structure of a link layer packet for anMPEG-2 TS packet and an encapsulation process thereof according to anembodiment of the present invention.

FIG. 13 illustrates an example of adaptation modes in IP headercompression according to an embodiment of the present invention(transmitting side).

FIG. 14 illustrates a link mapping table (LMT) and an RoHC-U descriptiontable according to an embodiment of the present invention.

FIG. 15 illustrates a structure of a link layer on a transmitter sideaccording to an embodiment of the present invention.

FIG. 16 illustrates a structure of a link layer on a receiver sideaccording to an embodiment of the present invention.

FIG. 17 illustrates a configuration of signaling transmission through alink layer according to an embodiment of the present invention(transmitting/receiving sides).

FIG. 18 is a block diagram illustrating a configuration of a broadcastsignal transmission apparatus for future broadcast services according toan embodiment of the present invention.

FIG. 19 is a block diagram illustrating a bit interleaved coding &modulation (BICM) block according to an embodiment of the presentinvention.

FIG. 20 is a block diagram illustrating a BICM block according toanother embodiment of the present invention.

FIG. 21 is a diagram illustrating a bit interleaving process of physicallayer signalling (PLS) according to an embodiment of the presentinvention.

FIG. 22 is a block diagram illustrating a configuration of a broadcastsignal reception apparatus for future broadcast services according to anembodiment of the present invention.

FIG. 23 is a diagram illustrating a signaling hierarchy structure of aframe according to an embodiment of the present invention.

FIG. 24 is a table illustrating PLS1 data according to an embodiment ofthe present invention.

FIG. 25 is a table illustrating PLS2 data according to an embodiment ofthe present invention.

FIG. 26 is a table illustrating PLS2 data according to anotherembodiment of the present invention.

FIG. 27 is a diagram illustrating a logical structure of a frameaccording to an embodiment of the present invention.

FIG. 28 is a diagram illustrating PLS mapping according to an embodimentof the present invention.

FIG. 29 is a diagram illustrating time interleaving according to anembodiment of the present invention.

FIG. 30 is a diagram illustrating a basic operation of a twistedrow-column block interleaver according to an embodiment of the presentinvention.

FIG. 31 is a diagram illustrating an operation of a twisted row-columnblock interleaver according to another embodiment of the presentinvention.

FIG. 32 is a block diagram illustrating an interlaving address generatorincluding a main pseudo-random binary sequence (PRBS) generator and asub-PRBS generator according to each FFT mode according to an embodimentof the present invention.

FIG. 33 is a diagram illustrating a main PRBS used for all FFT modesaccording to an embodiment of the present invention.

FIG. 34 is a diagram illustrating a sub-PRBS used for FFT modes and aninterleaving address for frequency interleaving according to anembodiment of the present invention.

FIG. 35 is a diagram illustrating a write operation of a timeinterleaver according to an embodiment of the present invention.

FIG. 36 is a table illustrating an interleaving type applied accordingto the number of PLPs.

FIG. 37 is a block diagram including a first example of a structure of ahybrid time interleaver.

FIG. 38 is a block diagram including a second example of the structureof the hybrid time interleaver.

FIG. 39 is a block diagram including a first example of a structure of ahybrid time deinterleaver.

FIG. 40 is a block diagram including a second example of the structureof the hybrid time deinterleaver.

FIG. 41 illustrates an application-related broadcast service accordingto an embodiment of the present invention.

FIG. 42 illustrates a part of an ApplicationList element according to anembodiment of the present invention.

FIG. 43 illustrates another part of the ApplicationList elementaccording to an embodiment of the present invention.

FIG. 44 illustrates an event message table (EMT) according to anembodiment of the present invention.

FIG. 45 illustrates a method of providing the broadcast service by atransmitting side according to an embodiment of the present invention.

FIG. 46 illustrates an apparatus for providing the broadcast service bythe transmitting side according to an embodiment of the presentinvention.

FIG. 47 illustrates an AST transmitted through a broadcast networkaccording to an embodiment of the present invention.

FIG. 48 illustrates an AST transmitted through a broadband networkaccording to an embodiment of the present invention.

FIG. 49 illustrates an event transmitted in the form of an EventStreamelement through the broadcast network according to an embodiment of thepresent invention.

FIG. 50 illustrates an event transmitted in the form of an emsg boxthrough the broadcast network according to an embodiment of the presentinvention.

FIG. 51 illustrates an event transmitted in the form of an EventStreamelement through the broadband network according to an embodiment of thepresent invention.

FIG. 52 illustrates an event transmitted in the form of an emsg boxthrough the broadband network according to an embodiment of the presentinvention.

FIG. 53 illustrates an API and an event listener according to anembodiment of the present invention.

FIG. 54 is a diagram illustrating a hierarchical signaling structureaccording to an embodiment of the present invention;

FIG. 55 is a diagram illustrating a transmission path of an FITaccording to an embodiment of the present invention;

FIG. 56 is a diagram illustrating a process for bootstrapping an SLSusing an FIT according to an embodiment of the present invention;

FIG. 57 is a diagram illustrating extension of 3DPP MBMS signaling for abroadcast system according to an embodiment of the present invention;

FIG. 58 is a diagram illustrating a protocol stack of a broadcast systemaccording to an embodiment of the present invention;

FIG. 59 is a diagram illustrating a relationship of a service managementlayer, a delivery layer, and physical layer entities according to anembodiment of the present invention;

FIG. 60 is a diagram illustrating a signaling structure of a broadcastsystem according to an embodiment of the present invention;

FIG. 61 is a diagram illustrating an FIT according to an embodiment ofthe present invention;

FIG. 62 is a diagram illustrating a position of a descriptor to beincluded in signaling for a broadcast system according to an embodimentof the present invention;

FIG. 63 is a diagram illustratingbroadcast_signaling_location_descriptor( ) according to an embodiment ofthe present invention;

FIG. 64 is a diagram illustrating the meaning ofinet_signaling_location_descriptor( ) and URL type information accordingto an embodiment of the present invention;

FIG. 65 is a diagram illustrating a query term using URL bytesinformation of inet_signaling_location_descriptor( ) according to anembodiment of the present invention;

FIG. 66 is a diagram illustrating capability_descriptor( ) according toan embodiment of the present invention;

FIG. 67 is a diagram illustrating an FIT defied in XML according to anembodiment of the present invention;

FIG. 68 is a diagram illustrating a data model for a linear serviceaccording to an embodiment of the present invention;

FIG. 69 is a diagram illustrating USBD according to an embodiment of thepresent invention;

FIG. 70 is a diagram illustrating S-TSID according to an embodiment ofthe present invention;

FIG. 71 is a diagram illustratingATSC_physical_layer_pipe_identifier_descriptor( ) according to anembodiment of the present invention;

FIG. 72 is a diagram illustrating a hierarchical signaling structure ofan ATSC3.0 system according to an embodiment of the present invention;

FIG. 73 is a diagram illustrating flow of a rapid channel scan operationaccording to an embodiment of the present invention;

FIG. 74 is a diagram illustrating flow of an entire channel scanningoperation according to an embodiment of the present invention;

FIG. 75 is a diagram illustrating a procedure for acquiring a service inpure broadcast according to an embodiment of the present invention;

FIG. 76 is a diagram illustrating a procedure for acquiring a servicethrough a plurality of ROUTE sessions in pure broadcast according to anembodiment of the present invention;

FIG. 77 is a diagram illustrating a procedure for bootstrappingelectronic service guide (ESG) through a broadband network according toan embodiment of the present invention;

FIG. 78 is a diagram illustrating a procedure for acquiring a servicethrough broadcast and broadband according to an embodiment of thepresent invention;

FIG. 79 is a diagram illustrating signaling for an operation forchanging reception of a service between broadcast and a broadbandaccording to an embodiment of the present invention;

FIG. 80 is a diagram illustrating signaling of receiver capabilityinformation according to an embodiment of the present invention;

FIG. 81 is a diagramming illustrating the meaning of a LCT transportobject identifier (TOI) field and information included in the field forfiltering of a fragment according to an embodiment of the presentinvention;

FIG. 82 is a diagram illustrating MetadataEnvelope of XML form forapplying template-based compression to signaling according to anembodiment of the present invention;

FIG. 83 is a diagram illustrating a compression procedure of atemplate-based signaling fragment according to an embodiment of thepresent invention;

FIG. 84 is a diagram illustratingbroadcast_signaling_location_descriptor( ) according to anotherembodiment of the present invention;

FIG. 85 illustrates a method of providing a broadcast service(transmitting side) according to an embodiment of the present invention.

FIG. 86 is a diagram illustrating an apparatus for providing a broadcastservice (transmitting side) according to an embodiment of the presentinvention.

DETAILED DESCRIPTION OF THE INVENTION

Reference will now be made in detail to the preferred embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings. The detailed description, which will be given below withreference to the accompanying drawings, is intended to explain exemplaryembodiments of the present invention, rather than to show the onlyembodiments that may be implemented according to the present invention.The following detailed description includes specific details in order toprovide a thorough understanding of the present invention. However, itwill be apparent to those skilled in the art that the present inventionmay be practiced without such specific details.

Although most terms used in the present invention have been selectedfrom general ones widely used in the art, some terms have beenarbitrarily selected by the applicant and their meanings are explainedin detail in the following description as needed. Thus, the presentinvention should be understood based upon the intended meanings of theterms rather than their simple names or meanings.

The present invention provides apparatuses and methods for transmittingand receiving broadcast signals for future broadcast services. Futurebroadcast services according to an embodiment of the present inventioninclude a terrestrial broadcast service, a mobile broadcast service, aUHDTV service, etc. The present invention may process broadcast signalsfor the future broadcast services through non-Multiple Input MultipleOutput (MIMO) or MIMO according to one embodiment. A non-MIMO schemeaccording to an embodiment of the present invention may include aMultiple Input Single Output (MISO) scheme, a Single Input Single Output(SISO) scheme, etc.

FIG. 1 illustrates a receiver protocol stack according to an embodimentof the present invention.

Two schemes may be used in broadcast service delivery through abroadcast network.

In a first scheme, Media Processing Units (MPUs) are transmitted using aMoving Picture Experts Group (MPEG) Media Transport Protocol (MMTP)based on MPEG Media Transport (MMT). In a second scheme, DynamicAdaptive Streaming over HTTP (DASH) segments may be transmitted using aReal-Time Object Delivery over Unidirectional Transport (ROUTE) protocolbased on MPEG DASH.

Non-timed content including NRT media, EPG data, and other files isdelivered with ROUTE. Signaling may be delivered over MMTP and/or ROUTE,while bootstrap signaling information is provided by the means of theService List Table (SLT).

In hybrid service delivery, MPEG DASH over HTTP/TCP/IP is used on thebroadband side. Media files in ISO Base Media File Format (BMFF) areused as the delivery, media encapsulation and synchronization format forboth broadcast and broadband delivery. Here, hybrid service delivery mayrefer to a case in which one or more program elements are deliveredthrough a broadband path.

Services are delivered using three functional layers. These are thePhysical layer, the Delivery layer and the Service Management layer. ThePhysical layer provides the mechanism by which signaling, serviceannouncement and IP packet streams are transported over the BroadcastPhysical layer and/or Broadband Physical layer. The Delivery layerprovides object and object flow transport functionality. It is enabledby the MMTP or the ROUTE protocol, operating on a UDP/IP multicast overthe Broadcast Physical layer, and enabled by the HTTP protocol on aTCP/IP unicast over the Broadband Physical layer. The Service Managementlayer enables any type of service, such as linear TV or HTML5application service, to be carried by the underlying Delivery andPhysical layers.

In this figure, a protocol stack part on a broadcast side may be dividedinto a part transmitted through the SLT and the MMTP, and a parttransmitted through ROUTE.

The SLT may be encapsulated through UDP and IP layers. Here, the SLTwill be described below. The MMTP may transmit data formatted in an MPUformat defined in MMT, and signaling information according to the MMTP.The data may be encapsulated through the UDP and IP layers. ROUTE maytransmit data formatted in a DASH segment form, signaling information,and non-timed data such as NRT data, etc. The data may be encapsulatedthrough the UDP and IP layers. According to a given embodiment, some orall processing according to the UDP and IP layers may be omitted. Here,the illustrated signaling information may be signaling informationrelated to a service.

The part transmitted through the SLT and the MMTP and the parttransmitted through ROUTE may be processed in the UDP and IP layers, andthen encapsulated again in a data link layer. The link layer will bedescribed below. Broadcast data processed in the link layer may bemulticast as a broadcast signal through processes such asencoding/interleaving, etc. in the physical layer.

In this figure, a protocol stack part on a broadband side may betransmitted through HTTP as described above. Data formatted in a DASHsegment form, signaling information, NRT information, etc. may betransmitted through HTTP. Here, the illustrated signaling informationmay be signaling information related to a service. The data may beprocessed through the TCP layer and the IP layer, and then encapsulatedinto the link layer. According to a given embodiment, some or all of theTCP, the IP, and the link layer may be omitted. Broadband data processedthereafter may be transmitted by unicast in the broadband through aprocess for transmission in the physical layer.

Service can be a collection of media components presented to the user inaggregate; components can be of multiple media types; a Service can beeither continuous or intermittent; a Service can be Real Time orNon-Real Time; Real Time Service can consist of a sequence of TVprograms.

FIG. 2 illustrates a relation between the SLT and SLS according to anembodiment of the present invention.

Service Signaling provides service discovery and descriptioninformation, and comprises two functional components: Bootstrapsignaling via the Service List Table (SLT) and the Service LayerSignaling (SLS). These represent the information which is necessary todiscover and acquire user services. The SLT enables the receiver tobuild a basic service list, and bootstrap the discovery of the SLS foreach service.

The SLT can enable very rapid acquisition of basic service information.The SLS enables the receiver to discover and access services and theircontent components. Details of the SLT and SLS will be described below.

As described in the foregoing, the SLT may be transmitted throughUDP/IP. In this instance, according to a given embodiment, datacorresponding to the SLT may be delivered through the most robust schemein this transmission.

The SLT may have access information for accessing SLS delivered by theROUTE protocol. In other words, the SLT may be bootstrapped into SLSaccording to the ROUTE protocol. The SLS is signaling informationpositioned in an upper layer of ROUTE in the above-described protocolstack, and may be delivered through ROUTE/UDP/IP. The SLS may betransmitted through one of LCT sessions included in a ROUTE session. Itis possible to access a service component corresponding to a desiredservice using the SLS.

In addition, the SLT may have access information for accessing an MMTsignaling component delivered by MMTP. In other words, the SLT may bebootstrapped into SLS according to the MMTP. The SLS may be delivered byan MMTP signaling message defined in MMT. It is possible to access astreaming service component (MPU) corresponding to a desired serviceusing the SLS. As described in the foregoing, in the present invention,an NRT service component is delivered through the ROUTE protocol, andthe SLS according to the MMTP may include information for accessing theROUTE protocol. In broadband delivery, the SLS is carried overHTTP(S)/TCP/IP.

FIG. 3 illustrates an SLT according to an embodiment of the presentinvention.

First, a description will be given of a relation among respectivelogical entities of service management, delivery, and a physical layer.

Services may be signaled as being one of two basic types. First type isa linear audio/video or audio-only service that may have an app-basedenhancement. Second type is a service whose presentation and compositionis controlled by a downloaded application that is executed uponacquisition of the service. The latter can be called an “app-based”service.

The rules regarding presence of ROUTE/LCT sessions and/or MMTP sessionsfor carrying the content components of a service may be as follows.

For a broadcast delivery of a Linear service without app-basedenhancement, the service's content components can be carried by either(but not both): (1) One or more ROUTE/LCT sessions, or (2) One or moreMMTP sessions.

For broadcast delivery of a Linear service with app-based enhancement,the service's content components can be carried by: (1) One or moreROUTE/LCT sessions, and (2) Zero or more MMTP sessions.

In certain embodiments, use of both MMTP and ROUTE for streaming mediacomponents in the same service may not be allowed.

For broadcast delivery of an App-based service, the service's contentcomponents can be carried by one or more ROUTE/LCT sessions.

Each ROUTE session comprises one or more LCT sessions which carry as awhole, or in part, the content components that make up the service. Instreaming services delivery, an LCT session may carry an individualcomponent of a user service such as an audio, video or closed captionstream. Streaming media is formatted as DASH Segments.

Each MMTP session comprises one or more MMTP packet flows which carryMMT signaling messages or as a whole, or in part, the content component.An MMTP packet flow may carry MMT signaling messages or componentsformatted as MPUs.

For the delivery of NRT User Services or system metadata, an LCT sessioncarries file-based content items. These content files may consist ofcontinuous (time-based) or discrete (non-time-based) media components ofan NRT service, or metadata such as Service Signaling or ESG fragments.Delivery of system metadata such as Service Signaling or ESG fragmentsmay also be achieved through the Signaling Message mode of MMTP.

A Broadcast Stream is the abstraction for an RF Channel, which isdefined in terms of a carrier frequency centered within a specifiedbandwidth. It is identified by the pair [geographic area, frequency]. APhysical Layer Pipe (PLP) corresponds to a portion of the RF channel.Each PLP has certain modulation and coding parameters. It is identifiedby a PLP identifier (PLPID), which is unique within the Broadcast Streamit belongs to. Here, PLP can be referred to as DP (Data Pipe).

Each service is identified by two forms of service identifier: a compactform that is used in the SLT and is unique only within the broadcastarea, and a globally unique form that is used in the SLS and the ESG. AROUTE Session is identified by a source IP Address, destination IPAddress and destination port number. An LCT session (associated with theservice component(s) it carries) is identified by a Transport SessionIdentifier (TSI) which is unique within the scope of the parent ROUTEsession. Properties common to the LCT sessions, and certain propertiesunique to individual LCT sessions, are given in a ROUTE signalingstructure called a Service-based Transport Session Instance Description(S-TSID), which is part of the Service Layer Signaling. Each LCT sessionis carried over a single Physical Layer Pipe. According to a givenembodiment, one LCT session may be transmitted through a plurality ofPLPs. Different LCT sessions of a ROUTE session may or may not becontained in different Physical Layer Pipes. Here, the ROUTE session maybe delivered through a plurality of PLPs. The properties described inthe S-TSID include the TSI value and PLPID for each LCT session,descriptors for the delivery objects/files, and Application Layer FECparameters.

A MMTP Session is identified by destination IP Address and destinationport number. An MMTP packet flow (associated with the servicecomponent(s) it carries) is identified by a packet_id which is uniquewithin the scope of the parent MMTP session. Properties common to eachMMTP packet flow, and certain properties of MMTP packet flows, are givenin the SLT. Properties for each MMTP session are given by MMT signalingmessages, which may be carried within the MMTP session. Different MMTPpacket flows of a MMTP session may or may not be contained in differentPhysical Layer Pipes. Here, the MMTP session may be delivered through aplurality of PLPs. The properties described in the MMT signalingmessages include the packet id value and PLPID for each MMTP packetflow. Here, the MMT signaling messages may have a form defined in MMT,or have a deformed form according to embodiments to be described below.

Hereinafter, a description will be given of low level signaling (LLS).

Signaling information which is carried in the payload of IP packets witha well-known address/port dedicated to this function is referred to asLow Level Signaling (LLS). The IP address and the port number may bedifferently configured depending on embodiments. In one embodiment, LLScan be transported in IP packets with address 224.0.23.60 anddestination port 4937/udp. LLS may be positioned in a portion expressedby “SLT” on the above-described protocol stack. However, according to agiven embodiment, the LLS may be transmitted through a separate physicalchannel (dedicated channel) in a signal frame without being subjected toprocessing of the UDP/IP layer.

UDP/IP packets that deliver LLS data may be formatted in a form referredto as an LLS table. A first byte of each UDP/IP packet that delivers theLLS data may correspond to a start of the LLS table. The maximum lengthof any LLS table is limited by the largest IP packet that can bedelivered from the PHY layer, 65,507 bytes.

The LLS table may include an LLS table ID field that identifies a typeof the LLS table, and an LLS table version field that identifies aversion of the LLS table. According to a value indicated by the LLStable ID field, the LLS table may include the above-described SLT or arating region table (RRT). The RRT may have information about contentadvisory rating.

Hereinafter, the SLT will be described. LLS can be signaling informationwhich supports rapid channel scans and bootstrapping of serviceacquisition by the receiver, and SLT can be a table of signalinginformation which is used to build a basic service listing and providebootstrap discovery of SLS.

The function of the SLT is similar to that of the Program AssociationTable (PAT) in MPEG-2 Systems, and the Fast Information Channel (FIC)found in ATSC Systems. For a receiver first encountering the broadcastemission, this is the place to start. SLT supports a rapid channel scanwhich allows a receiver to build a list of all the services it canreceive, with their channel name, channel number, etc., and SLT providesbootstrap information that allows a receiver to discover the SLS foreach service. For ROUTE/DASH-delivered services, the bootstrapinformation includes the destination IP address and destination port ofthe LCT session that carries the SLS. For MMT/MPU-delivered services,the bootstrap information includes the destination IP address anddestination port of the MMTP session carrying the SLS.

The SLT supports rapid channel scans and service acquisition byincluding the following information about each service in the broadcaststream. First, the SLT can include information necessary to allow thepresentation of a service list that is meaningful to viewers and thatcan support initial service selection via channel number or up/downselection. Seconds, the SLT can include information necessary to locatethe Service Layer Signaling for each service listed. That is, the SLTmay include access information related to a location at which the SLS isdelivered.

The illustrated SLT according to the present embodiment is expressed asan XML document having an SLT root element. According to a givenembodiment, the SLT may be expressed in a binary format or an XMLdocument.

The SLT root element of the SLT illustrated in the figure may include@bsid, @sltSectionVersion, @sltSectionNumber, @total SltSectionNumbers,@language, @capabilities, InetSigLoc and/or Service. According to agiven embodiment, the SLT root element may further include @providerId.According to a given embodiment, the SLT root element may not include@language.

The service element may include @serviceId, @SLTserviceSeqNumber,@protected, @majorChannelNo, @minorChannelNo, @serviceCategory,@shortServiceName, @hidden, @slsProtocolType, BroadcastSignaling,@slsPlpId, @slsDestinationIpAddress, @slsDestinationUdpPort,@slsSourceIpAddress, @slsMajorProtocolVersion, @SlsMinorProtocolVersion,@serviceLanguage, @broadbandAccessRequired, @capabilities and/orInetSigLoc.

According to a given embodiment, an attribute or an element of the SLTmay be added/changed/deleted. Each element included in the SLT mayadditionally have a separate attribute or element, and some attribute orelements according to the present embodiment may be omitted. Here, afield which is marked with @ may correspond to an attribute, and a fieldwhich is not marked with @ may correspond to an element.

@bsid is an identifier of the whole Broadcast Stream. The value of BSIDmay be unique on a regional level.

@providerId can be an index of broadcaster that is using part or all ofthis broadcast stream. This is an optional attribute. When it's notpresent, it means that this broadcast stream is being used by onebroadcaster. @providerId is not illustrated in the figure.

@sltSectionVersion can be a version number of the SLT section. ThesltSectionVersion can be incremented by 1 when a change in theinformation carried within the slt occurs. When it reaches maximumvalue, it wraps around to 0.

@sltSectionNumber can be the number, counting from 1, of this section ofthe SLT. In other words, @sltSectionNumber may correspond to a sectionnumber of the SLT section. When this field is not used,@sltSectionNumber may be set to a default value of 1.

@totalSltSectionNumbers can be the total number of sections (that is,the section with the highest sltSectionNumber) of the SLT of which thissection is part. sltSectionNumber and totalSltSectionNumbers togethercan be considered to indicate “Part M of N” of one portion of the SLTwhen it is sent in fragments. In other words, when the SLT istransmitted, transmission through fragmentation may be supported. Whenthis field is not used, @totalSltSectionNumbers may be set to a defaultvalue of 1. A case in which this field is not used may correspond to acase in which the SLT is not transmitted by being fragmented.

@language can indicate primary language of the services included in thisslt instance. According to a given embodiment, a value of this field mayhave be a three-character language code defined in the ISO. This fieldmay be omitted.

@capabilities can indicate required capabilities for decoding andmeaningfully presenting the content for all the services in this sltinstance.

InetSigLoc can provide a URL telling the receiver where it can acquireany requested type of data from external server(s) via broadband. Thiselement may include @urlType as a lower field. According to a value ofthe @urlType field, a type of a URL provided by InetSigLoc may beindicated. According to a given embodiment, when the @urlType field hasa value of 0, InetSigLoc may provide a URL of a signaling server. Whenthe @urlType field has a value of 1, InetSigLoc may provide a URL of anESG server. When the @urlType field has other values, the field may bereserved for future use.

The service field is an element having information about each service,and may correspond to a service entry. Service element fieldscorresponding to the number of services indicated by the SLT may bepresent. Hereinafter, a description will be given of a lowerattribute/element of the service field.

@serviceId can be an integer number that uniquely identify this Servicewithin the scope of this Broadcast area. According to a givenembodiment, a scope of @serviceId may be changed. @SLTserviceSeqNumbercan be an integer number that indicates the sequence number of the SLTservice information with service ID equal to the serviceId attributeabove. SLTserviceSeqNumber value can start at 0 for each service and canbe incremented by 1 every time any attribute in this Service element ischanged. If no attribute values are changed compared to the previousService element with a particular value of ServiceID thenSLTserviceSeqNumber would not be incremented. The SLTserviceSeqNumberfield wraps back to 0 after reaching the maximum value.

@protected is flag information which may indicate whether one or morecomponents for significant reproduction of the service are in aprotected state. When set to “1” (true), that one or more componentsnecessary for meaningful presentation is protected. When set to “0”(false), this flag indicates that no components necessary for meaningfulpresentation of the service are protected. Default value is false.

@majorChannelNo is an integer number representing the “major” channelnumber of the service. An example of the field may have a range of 1 to999.

@minorChannelNo is an integer number representing the “minor” channelnumber of the service. An example of the field may have a range of 1 to999.

@serviceCategory can indicate the category of this service. This fieldmay indicate a type that varies depending on embodiments. According to agiven embodiment, when this field has values of 1, 2, and 3, the valuesmay correspond to a linear A/V service, a linear audio only service, andan app-based service, respectively. When this field has a value of 0,the value may correspond to a service of an undefined category. Whenthis field has other values except for 1, 2, and 3, the field may bereserved for future use. @shortServiceName can be a short string name ofthe Service.

@hidden can be boolean value that when present and set to “true”indicates that the service is intended for testing or proprietary use,and is not to be selected by ordinary TV receivers. The default value is“false” when not present.

@slsProtocolType can be an attribute indicating the type of protocol ofService Layer Signaling used by this service. This field may indicate atype that varies depending on embodiments. According to a givenembodiment, when this field has values of 1 and 2, protocols of SLS usedby respective corresponding services may be ROUTE and MMTP,respectively. When this field has other values except for 0, the fieldmay be reserved for future use. This field may be referred to as@slsProtocol.

BroadcastSignaling and lower attributes/elements thereof may provideinformation related to broadcast signaling. When the BroadcastSignalingelement is not present, the child element InetSigLoc of the parentService element can be present and its attribute urlType includesURL_type 0x00 (URL to signaling server). In this case attribute urlsupports the query parameter svc=<service_id> where service_idcorresponds to the serviceId attribute for the parent Service element.

Alternatively when the BroadcastSignaling element is not present, theelement InetSigLoc can be present as a child element of the slt rootelement and the attribute urlType of that InetSigLoc element includesURL_type 0x00 (URL to signaling server). In this case attribute url forURL_type 0x00 supports the query parameter svc=<service_id> whereservice_id corresponds to the serviceId attribute for the parent Serviceelement.

@slsPlpId can be a string representing an integer number indicating thePLP ID of the physical layer pipe carrying the SLS for this service.

@slsDestinationIpAddress can be a string containing the dotted-IPv4destination address of the packets carrying SLS data for this service.

@slsDestinationUdpPort can be a string containing the port number of thepackets carrying SLS data for this service. As described in theforegoing, SLS bootstrapping may be performed by destination IP/UDPinformation.

@slsSourceIpAddress can be a string containing the dotted-IPv4 sourceaddress of the packets carrying SLS data for this service.

@slsMajorProtocolVersion can be major version number of the protocolused to deliver the Service Layer Signaling for this service. Defaultvalue is 1.

@SlsMinorProtocolVersion can be minor version number of the protocolused to deliver the Service Layer Signalling for this service. Defaultvalue is 0.

@serviceLanguage can be a three-character language code indicating theprimary language of the service. A value of this field may have a formthat varies depending on embodiments.

@broadbandAccessRequired can be a Boolean indicating that broadbandaccess is required for a receiver to make a meaningful presentation ofthe service. Default value is false. When this field has a value ofTrue, the receiver needs to access a broadband for significant servicereproduction, which may correspond to a case of hybrid service delivery.

@capabilities can represent required capabilities for decoding andmeaningfully presenting the content for the service with service IDequal to the serviceId attribute above.

InetSigLoc can provide a URL for access to signaling or announcementinformation via broadband, if available. Its datatype can be anextension of the anyURL datatype, adding an @urlType attribute thatindicates what the URL gives access to. An @urlType field of this fieldmay indicate the same meaning as that of the @urlType field ofInetSigLoc described above. When an InetSigLoc element of attribute URLtype 0x00 is present as an element of the SLT, it can be used to makeHTTP requests for signaling metadata. The HTTP POST message body mayinclude a service term. When the InetSigLoc element appears at thesection level, the service term is used to indicate the service to whichthe requested signaling metadata objects apply. If the service term isnot present, then the signaling metadata objects for all services in thesection are requested. When the InetSigLoc appears at the service level,then no service term is needed to designate the desired service. When anInetSigLoc element of attribute URL_type 0x01 is provided, it can beused to retrieve ESG data via broadband. If the element appears as achild element of the service element, then the URL can be used toretrieve ESG data for that service. if the element appears as a childelement of the SLT element, then the URL can be used to retrieve ESGdata for all services in that section.

In another example of the SLT, @sltSectionVersion, @sltSectionNumber,@totalSltSectionNumbers and/or @language fields of the SLT may beomitted.

In addition, the above-described InetSigLoc field may be replaced by@sltInetSigUri and/or @sltInetEsgUri field. The two fields may includethe URI of the signaling server and URI information of the ESG server,respectively. The InetSigLoc field corresponding to a lower field of theSLT and the InetSigLoc field corresponding to a lower field of theservice field may be replaced in a similar manner.

The suggested default values may vary depending on embodiments. Anillustrated “use” column relates to the respective fields. Here, “1” mayindicate that a corresponding field is an essential field, and “0 . . .1” may indicate that a corresponding field is an optional field.

FIG. 4 illustrates SLS bootstrapping and a service discovery processaccording to an embodiment of the present invention.

Hereinafter, SLS will be described.

SLS can be signaling which provides information for discovery andacquisition of services and their content components.

For ROUTE/DASH, the SLS for each service describes characteristics ofthe service, such as a list of its components and where to acquire them,and the receiver capabilities required to make a meaningful presentationof the service. In the ROUTE/DASH system, the SLS includes the UserService Bundle Description (USBD), the S-TSID and the DASH MediaPresentation Description (MPD). Here, USBD or user service description(USD) is one of SLS XML fragments, and may function as a signaling herbthat describes specific descriptive information. USBD/USD may beextended beyond 3GPP MBMS. Details of USBD/USD will be described below.

The Service Signaling focuses on basic attributes of the service itself,especially those attributes needed to acquire the service. Properties ofthe service and programming that are intended for viewers appear asService Announcement, or ESG data.

Having separate Service Signaling for each service permits a receiver toacquire the appropriate SLS for a service of interest without the needto parse the entire SLS carried within a Broadcast Stream.

For optional broadband delivery of Service Signaling, the SLT caninclude HTTP URLs where the Service Signaling files can be obtained, asdescribed above.

LLS is used for bootstrapping SLS acquisition, and subsequently, the SLSis used to acquire service components delivered on either ROUTE sessionsor MMTP sessions. The described figure illustrates the followingsignaling sequences. Receiver starts acquiring the SLT described above.Each service identified by service_id delivered over ROUTE sessionsprovides SLS bootstrapping information: PLPID(#1), source IP address(siP1), destination IP address (diP1), and destination port number(dPort1). Each service identified by service_id delivered over MMTPsessions provides SLS bootstrapping information: PLPID(#2), destinationIP address (diP2), and destination port number (dPort2).

For streaming services delivery using ROUTE, the receiver can acquireSLS fragments carried over the IP/UDP/LCT session and PLP; whereas forstreaming services delivery using MMTP, the receiver can acquire SLSfragments carried over an MMTP session and PLP. For service deliveryusing ROUTE, these SLS fragments include USBD/USD fragments, S-TSIDfragments, and MPD fragments. They are relevant to one service. USBD/USDfragments describes service layer properties and provide URI referencesto S-TSID fragments and URI references to MPD fragments. In other words,the USBD/USD may refer to S-TSID and MPD. For service delivery usingMMTP, the USBD references the MMT Signaling's MPT Message, the MP Tableof which provides identification of Package ID and location informationfor assets belonging to the service. Here, an asset is a multimedia dataentity, and may refer to a data entity which is combined into one uniqueID and is used to generate one multimedia presentation. The asset maycorrespond to a service component included in one service. The MPTmessage is a message having the MP table of MMT. Here, the MP table maybe an MMT package table having information about content and an MMTasset. Details may be similar to a definition in MMT. Here, mediapresentation may correspond to a collection of data that establishesbounded/unbounded presentation of media content.

The S-TSID fragment provides component acquisition informationassociated with one service and mapping between DASH Representationsfound in the MPD and in the TSI corresponding to the component of theservice. The S-TSID can provide component acquisition information in theform of a TSI and the associated DASH Representation identifier, andPLPID carrying DASH Segments associated with the DASH Representation. Bythe PLPID and TSI values, the receiver collects the audio/videocomponents from the service and begins buffering DASH Media Segmentsthen applies the appropriate decoding processes.

For USBD listing service components delivered on MMTP sessions, asillustrated by “Service #2” in the described figure, the receiver alsoacquires an MPT message with matching MMT_package_id to complete theSLS. An MPT message provides the full list of service componentscomprising a service and the acquisition information for each component.Component acquisition information includes MMTP session information, thePLPID carrying the session and the packet_id within that session.

According to a given embodiment, for example, in ROUTE, two or moreS-TSID fragments may be used. Each fragment may provide accessinformation related to LCT sessions delivering content of each service.

In ROUTE, S-TSID, USBD/USD, MPD, or an LCT session delivering S-TSID,USBD/USD or MPD may be referred to as a service signaling channel. InMMTP, USBD/UD, an MMT signaling message, or a packet flow delivering theMMTP or USBD/UD may be referred to as a service signaling channel.

Unlike the illustrated example, one ROUTE or MMTP session may bedelivered through a plurality of PLPs. In other words, one service maybe delivered through one or more PLPs. As described in the foregoing,one LCT session may be delivered through one PLP. Unlike the figure,according to a given embodiment, components included in one service maybe delivered through different ROUTE sessions. In addition, according toa given embodiment, components included in one service may be deliveredthrough different MMTP sessions. According to a given embodiment,components included in one service may be delivered separately through aROUTE session and an MMTP session. Although not illustrated, componentsincluded in one service may be delivered via broadband (hybriddelivery).

FIG. 5 illustrates a USBD fragment for ROUTE/DASH according to anembodiment of the present invention.

Hereinafter, a description will be given of SLS in delivery based onROUTE.

Service Layer Signaling provides detailed technical information to thereceiver to enable the discovery and access of services and theircontent components. It can include a set of XML-encoded metadatafragments carried over a dedicated LCT session. That LCT session can beacquired using the bootstrap information contained in the SLT asdescribed above. The SLS is defined on a per-service level, and itdescribes the characteristics and access information of the service,such as a list of its content components and how to acquire them, andthe receiver capabilities required to make a meaningful presentation ofthe service. In the ROUTE/DASH system, for linear services delivery, theSLS consists of the following metadata fragments: USBD, S-TSID and theDASH MPD. The SLS fragments can be delivered on a dedicated LCTtransport session with TSI=0. According to a given embodiment, a TSI ofa particular LCT session (dedicated LCT session) in which an SLSfragment is delivered may have a different value. According to a givenembodiment, an LCT session in which an SLS fragment is delivered may besignaled using the SLT or another scheme.

ROUTE/DASH Service Layer Signaling can include the User Service BundleDescription (USBD) and Service-based Transport Session InstanceDescription (S-TSID) metadata fragments. These service signalingfragments are applicable to both linear and application-based services.The USBD fragment contains service identification, device capabilitiesinformation, references to other SLS fragments required to access theservice and constituent media components, and metadata to enable thereceiver to determine the transport mode (broadcast and/or broadband) ofservice components. The S-TSID fragment, referenced by the USBD,provides transport session descriptions for the one or more ROUTE/LCTsessions in which the media content components of a service aredelivered, and descriptions of the delivery objects carried in those LCTsessions. The USBD and S-TSID will be described below.

In streaming content signaling in ROUTE-based delivery, a streamingcontent signaling component of SLS corresponds to an MPD fragment. TheMPD is typically associated with linear services for the delivery ofDASH Segments as streaming content. The MPD provides the resourceidentifiers for individual media components of the linear/streamingservice in the form of Segment URLs, and the context of the identifiedresources within the Media Presentation. Details of the MPD will bedescribed below.

In app-based enhancement signaling in ROUTE-based delivery, app-basedenhancement signaling pertains to the delivery of app-based enhancementcomponents, such as an application logic file, locally-cached mediafiles, an network content items, or a notification stream. Anapplication can also retrieve locally-cached data over a broadbandconnection when available.

Hereinafter, a description will be given of details of USBD/USDillustrated in the figure.

The top level or entry point SLS fragment is the USBD fragment. Anillustrated USBD fragment is an example of the present invention, basicfields of the USBD fragment not illustrated in the figure may beadditionally provided according to a given embodiment. As described inthe foregoing, the illustrated USBD fragment has an extended form, andmay have fields added to a basic configuration.

The illustrated USBD may have a bundleDescription root element. ThebundleDescription root element may have a userServiceDescriptionelement. The userServiceDescription element may correspond to aninstance for one service.

The userServiceDescription element may include @serviceId,@atsc:serviceId, @atsc: serviceStatus, @atsc:fullMPDUri, @atsc:sTSIDUri,name, serviceLanguage, atsc:capabilityCode and/or deliveryMethod.

@serviceId can be a globally unique URI that identifies a service,unique within the scope of the BSID. This parameter can be used to linkto ESG data (Service@globalServiceID).

@atsc:serviceId is a reference to corresponding service entry inLLS(SLT). The value of this attribute is the same value of serviceIdassigned to the entry.

@atsc:serviceStatus can specify the status of this service. The valueindicates whether this service is active or inactive. When set to “1”(true), that indicates service is active. When this field is not used,@atsc:serviceStatus may be set to a default value of 1.

@atsc:fullMPDUri can reference an MPD fragment which containsdescriptions for contents components of the service delivered overbroadcast and optionally, also over broadband.

@atsc:sTSIDUri can reference the S-TSID fragment which provides accessrelated parameters to the Transport sessions carrying contents of thisservice.

name can indicate name of the service as given by the lang attribute.name element can include lang attribute, which indicating language ofthe service name. The language can be specified according to XMLdatatypes.

serviceLanguage can represent available languages of the service. Thelanguage can be specified according to XML datatypes.

atsc:capabilityCode can specify the capabilities required in thereceiver to be able to create a meaningful presentation of the contentof this service. According to a given embodiment, this field may specifya predefined capability group. Here, the capability group may be a groupof capability attribute values for significant presentation. This fieldmay be omitted according to a given embodiment.

deliveryMethod can be a container of transport related informationpertaining to the contents of the service over broadcast and(optionally) broadband modes of access. Referring to data included inthe service, when the number of the data is N, delivery schemes forrespective data may be described by this element. The deliveryMethod mayinclude an r12:broadcastAppService element and an r12:unicastAppServiceelement. Each lower element may include a basePattern element as a lowerelement.

r12:broadcastAppService can be a DASH Representation delivered overbroadcast, in multiplexed or non-multiplexed form, containing thecorresponding media component(s) belonging to the service, across allPeriods of the affiliated Media Presentation. In other words, each ofthe fields may indicate DASH representation delivered through thebroadcast network.

r12:unicastAppService can be a DASH Representation delivered overbroadband, in multiplexed or non-multiplexed form, containing theconstituent media content component(s) belonging to the service, acrossall Periods of the affiliated Media Presentation. In other words, eachof the fields may indicate DASH representation delivered via broadband.

basePattern can be a character pattern for use by the the receiver tomatch against any portion of the Segment URL used by the DASH client torequest Media Segments of a parent Representation under its containingPeriod. A match implies that the corresponding requested Media Segmentis carried over broadcast transport. In a URL address for receiving DASHrepresentation expressed by each of the r12:broadcastAppService elementand the r12:unicastAppService element, a part of the URL, etc. may havea particular pattern. The pattern may be described by this field. Somedata may be distinguished using this information. The proposed defaultvalues may vary depending on embodiments. The “use” column illustratedin the figure relates to each field. Here, M may denote an essentialfield, O may denote an optional field, OD may denote an optional fieldhaving a default value, and CM may denote a conditional essential field.0 . . . 1 to 0 . . . N may indicate the number of available fields.

FIG. 6 illustrates an S-TSID fragment for ROUTE/DASH according to anembodiment of the present invention.

Hereinafter, a description will be given of the S-TSID illustrated inthe figure in detail.

S-TSID can be an SLS XML fragment which provides the overall sessiondescription information for transport session(s) which carry the contentcomponents of a service. The S-TSID is the SLS metadata fragment thatcontains the overall transport session description information for thezero or more ROUTE sessions and constituent LCT sessions in which themedia content components of a service are delivered. The S-TSID alsoincludes file metadata for the delivery object or object flow carried inthe LCT sessions of the service, as well as additional information onthe payload formats and content components carried in those LCTsessions.

Each instance of the S-TSID fragment is referenced in the USBD fragmentby the @atsc:sTSIDUri attribute of the userServiceDescription element.The illustrated S-TSID according to the present embodiment is expressedas an XML document. According to a given embodiment, the S-TSID may beexpressed in a binary format or as an XML document.

The illustrated S-TSID may have an S-TSID root element. The S-TSID rootelement may include @serviceId and/or RS.

@serviceID can be a reference corresponding service element in the USD.The value of this attribute can reference a service with a correspondingvalue of service_id.

The RS element may have information about a ROUTE session for deliveringthe service data. Service data or service components may be deliveredthrough a plurality of ROUTE sessions, and thus the number of RSelements may be 1 to N.

The RS element may include @bsid, @sIpAddr, @dIpAddr, @dport, @PLPIDand/or LS.

@bsid can be an identifier of the Broadcast Stream within which thecontent component(s) of the broadcastAppService are carried. When thisattribute is absent, the default Broadcast Stream is the one whose PLPscarry SLS fragments for this service. Its value can be identical to thatof the broadcast stream id in the SLT.

@sIpAddr can indicate source IP address. Here, the source IP address maybe a source IP address of a ROUTE session for delivering a servicecomponent included in the service. As described in the foregoing,service components of one service may be delivered through a pluralityof ROUTE sessions. Thus, the service components may be transmitted usinganother ROUTE session other than the ROUTE session for delivering theS-TSID. Therefore, this field may be used to indicate the source IPaddress of the ROUTE session. A default value of this field may be asource IP address of a current ROUTE session. When a service componentis delivered through another ROUTE session, and thus the ROUTE sessionneeds to be indicated, a value of this field may be a value of a sourceIP address of the ROUTE session. In this case, this field may correspondto M, that is, an essential field.

@dIpAddr can indicate destination IP address. Here, a destination IPaddress may be a destination IP address of a ROUTE session that deliversa service component included in a service. For a similar case to theabove description of @sIpAddr, this field may indicate a destination IPaddress of a ROUTE session that delivers a service component. A defaultvalue of this field may be a destination IP address of a current ROUTEsession. When a service component is delivered through another ROUTEsession, and thus the ROUTE session needs to be indicated, a value ofthis field may be a value of a destination IP address of the ROUTEsession. In this case, this field may correspond to M, that is, anessential field.

@dport can indicate destination port. Here, a destination port may be adestination port of a ROUTE session that delivers a service componentincluded in a service. For a similar case to the above description of@sIpAddr, this field may indicate a destination port of a ROUTE sessionthat delivers a service component. A default value of this field may bea destination port number of a current ROUTE session. When a servicecomponent is delivered through another ROUTE session, and thus the ROUTEsession needs to be indicated, a value of this field may be adestination port number value of the ROUTE session. In this case, thisfield may correspond to M, that is, an essential field.

@PLPID may be an ID of a PLP for a ROUTE session expressed by an RS. Adefault value may be an ID of a PLP of an LCT session including acurrent S-TSID. According to a given embodiment, this field may have anID value of a PLP for an LCT session for delivering an S-TSID in theROUTE session, and may have ID values of all PLPs for the ROUTE session.

An LS element may have information about an LCT session for delivering aservice data. Service data or service components may be deliveredthrough a plurality of LCT sessions, and thus the number of LS elementsmay be 1 to N.

The LS element may include @tsi, @PLPID, @bw, @startTime, @endTime,SrcFlow and/or RprFlow.

@tsi may indicate a TSI value of an LCT session for delivering a servicecomponent of a service.

@PLPID may have ID information of a PLP for the LCT session. This valuemay be overwritten on a basic ROUTE session value.

@bw may indicate a maximum bandwidth value. @startTime may indicate astart time of the LCT session. @endTime may indicate an end time of theLCT session. A SrcFlow element may describe a source flow of ROUTE. ARprFlow element may describe a repair flow of ROUTE.

The proposed default values may be varied according to an embodiment.The “use” column illustrated in the figure relates to each field. Here,M may denote an essential field, O may denote an optional field, OD maydenote an optional field having a default value, and CM may denote aconditional essential field. 0 . . . 1 to 0 . . . N may indicate thenumber of available fields.

Hereinafter, a description will be given of MPD for ROUTE/DASH.

The MPD is an SLS metadata fragment which contains a formalizeddescription of a DASH Media Presentation, corresponding to a linearservice of a given duration defined by the broadcaster (for example asingle TV program, or the set of contiguous linear TV programs over aperiod of time). The contents of the MPD provide the resourceidentifiers for Segments and the context for the identified resourceswithin the Media Presentation. The data structure and semantics of theMPD fragment can be according to the MPD defined by MPEG DASH.

One or more of the DASH Representations conveyed in the MPD can becarried over broadcast. The MPD may describe additional Representationsdelivered over broadband, e.g. in the case of a hybrid service, or tosupport service continuity in handoff from broadcast to broadcast due tobroadcast signal degradation (e.g. driving through a tunnel).

FIG. 7 illustrates a USBD/USD fragment for MMT according to anembodiment of the present invention.

MMT Service Layer Signaling for linear services comprise the USBDfragment and the MMT Package (MP) table. The MP table is as describedabove. The USBD fragment contains service identification, devicecapabilities information, references to other SLS information requiredto access the service and constituent media components, and the metadatato enable the receiver to determine the transport mode (broadcast and/orbroadband) of the service components. The MP table for MPU components,referenced by the USBD, provides transport session descriptions for theMMTP sessions in which the media content components of a service aredelivered and the descriptions of the Assets carried in those MMTPsessions.

The streaming content signaling component of the SLS for MPU componentscorresponds to the MP table defined in MMT. The MP table provides a listof MMT Assets where each Asset corresponds to a single service componentand the description of the location information for this component.

USBD fragments may also contain references to the S-TSID and the MPD asdescribed above, for service components delivered by the ROUTE protocoland the broadband, respectively. According to a given embodiment, indelivery through MMT, a service component delivered through the ROUTEprotocol is NRT data, etc. Thus, in this case, MPD may be unnecessary.In addition, in delivery through MMT, information about an LCT sessionfor delivering a service component, which is delivered via broadband, isunnecessary, and thus an S-TSID may be unnecessary. Here, an MMT packagemay be a logical collection of media data delivered using MMT. Here, anMMTP packet may refer to a formatted unit of media data delivered usingMMT. An MPU may refer to a generic container of independently decodabletimed/non-timed data. Here, data in the MPU is media codec agnostic.

Hereinafter, a description will be given of details of the USBD/USDillustrated in the figure.

The illustrated USBD fragment is an example of the present invention,and basic fields of the USBD fragment may be additionally providedaccording to an embodiment. As described in the foregoing, theillustrated USBD fragment has an extended form, and may have fieldsadded to a basic structure.

The illustrated USBD according to an embodiment of the present inventionis expressed as an XML document. According to a given embodiment, theUSBD may be expressed in a binary format or as an XML document.

The illustrated USBD may have a bundleDescription root element. ThebundleDescription root element may have a userServiceDescriptionelement. The userServiceDescription element may be an instance for oneservice.

The userServiceDescription element may include @serviceId,@atsc:serviceId, name, serviceLanguage, atsc:capabilityCode,atsc:Channel, atsc:mpuComponent, atsc:routeComponent,atsc:broadbandComponent and/or atsc:ComponentInfo.

Here, @serviceId, @atsc:serviceId, name, serviceLanguage, andatsc:capabilityCode may be as described above. The lang field below thename field may be as described above. atsc:capabilityCode may be omittedaccording to a given embodiment.

The userServiceDescription element may further include anatsc:contentAdvisoryRating element according to an embodiment. Thiselement may be an optional element. atsc:contentAdvisoryRating canspecify the content advisory rating. This field is not illustrated inthe figure.

atsc:Channel may have information about a channel of a service. Theatsc:Channel element may include @atsc:majorChannelNo,@atsc:minorChannelNo, @atsc:serviceLang, @atsc: serviceGenre, @atsc:serviceIcon and/or atsc: ServiceDescription. @atsc:majorChannelNo,@atsc:minorChannelNo, and @atsc:serviceLang may be omitted according toa given embodiment.

@atsc:majorChannelNo is an attribute that indicates the major channelnumber of the service.

@atsc:minorChannelNo is an attribute that indicates the minor channelnumber of the service.

@atsc:serviceLang is an attribute that indicates the primary languageused in the service.

@atsc:serviceGenre is an attribute that indicates primary genre of theservice.

@atsc:serviceIcon is an attribute that indicates the Uniform ResourceLocator (URL) for the icon used to represent this service.

atsc:ServiceDescription includes service description, possibly inmultiple languages. atsc: ServiceDescription includes can include @atsc:serviceDescrText and/or @atsc: serviceDescrLang.

@atsc:serviceDescrText is an attribute that indicates description of theservice.

@atsc:serviceDescrLang is an attribute that indicates the language ofthe serviceDescrText attribute above.

atsc:mpuComponent may have information about a content component of aservice delivered in a form of an MPU. atsc:mpuComponent may include@atsc:mmtPackageId and/or @atsc:nextMmtPackageId.

@atsc:mmtPackageId can reference a MMT Package for content components ofthe service delivered as MPUs.

@atsc:nextMmtPackageId can reference a MMT Package to be used after theone referenced by @atsc:mmtPackageId in time for content components ofthe service delivered as MPUs.

atsc:routeComponent may have information about a content component of aservice delivered through ROUTE. atsc:routeComponent may include@atsc:sTSIDUri, @sTSIDPlpId, @sTSIDDestinationIpAddress,@sTSIDDestinationUdpPort, @sTSIDSourceIpAddress,@sTSIDMajorProtocolVersion and/or @sTSIDMinorProtocolVersion.

@atsc:sTSIDUri can be a reference to the S-TSID fragment which providesaccess related parameters to the Transport sessions carrying contents ofthis service. This field may be the same as a URI for referring to anS-TSID in USBD for ROUTE described above. As described in the foregoing,in service delivery by the MMTP, service components, which are deliveredthrough NRT, etc., may be delivered by ROUTE. This field may be used torefer to the S-TSID therefor.

@sTSIDPlpId can be a string representing an integer number indicatingthe PLP ID of the physical layer pipe carrying the S-TSID for thisservice. (default: current physical layer pipe)

@sTSIDDestinationIpAddress can be a string containing the dotted-IPv4destination address of the packets carrying S-TSID for this service.(default: current MMTP session's source IP address)

@sTSIDDestinationUdpPort can be a string containing the port number ofthe packets carrying S-TSID for this service.

@sTSIDSourceIpAddress can be a string containing the dotted-IPv4 sourceaddress of the packets carrying S-TSID for this service.

@sTSIDMajorProtocolVersion can indicate major version number of theprotocol used to deliver the S-TSID for this service. Default value is1.

@sTSIDMinorProtocolVersion can indicate minor version number of theprotocol used to deliver the S-TSID for this service. Default value is0.

atsc:broadbandComponent may have information about a content componentof a service delivered via broadband. In other words,atsc:broadbandComponent may be a field on the assumption of hybriddelivery. atsc:broadbandComponent may further include @atsc:fullfMPDUri.

@atsc:fullfMPDUri can be a reference to an MPD fragment which containsdescriptions for contents components of the service delivered overbroadband.

An atsc:ComponentInfo field may have information about an availablecomponent of a service. The atsc:ComponentInfo field may haveinformation about a type, a role, a name, etc. of each component. Thenumber of atsc:ComponentInfo fields may correspond to the number (N) ofrespective components. The atsc:ComponentInfo field may include@atsc:componentType, @atsc:componentRole, @atsc: componentProtectedFlag,@atsc:componentId and/or @atsc:componentName.

@atsc:componentType is an attribute that indicates the type of thiscomponent. Value of 0 indicates an audio component. Value of 1 indicatesa video component. Value of 2 indicated a closed caption component.Value of 3 indicates an application component. Values 4 to 7 arereserved. A meaning of a value of this field may be differently setdepending on embodiments.

@atsc:componentRole is an attribute that indicates the role or kind ofthis component.

For audio (when componentType attribute above is equal to 0): values ofcomponentRole attribute are as follows: 0=Complete main, 1=Music andEffects, 2=Dialog, 3=Commentary, 4=Visually Impaired, 5=HearingImpaired, 6=Voice-Over, 7-254=reserved, 255=unknown. For Video (whencomponentType attribute above is equal to 1) values of componentRoleattribute are as follows: 0=Primary video, 1=Alternative camera view,2=Other alternative video component, 3=Sign language inset, 4=Followsubject video, 5=3D video left view, 6=3D video right view, 7=3D videodepth information, 8=Part of video array <x,y> of <n,m>,9=Follow-Subject metadata, 10-254=reserved, 255=unknown.

For Closed Caption component (when componentType attribute above isequal to 2) values of componentRole attribute are as follows: 0=Normal,1=Easy reader, 2-254=reserved, 255=unknown.

When componentType attribute above is between 3 to 7, inclusive, thecomponentRole can be equal to 255. A meaning of a value of this fieldmay be differently set depending on embodiments.

@atsc:componentProtectedFlag is an attribute that indicates if thiscomponent is protected (e.g. encrypted). When this flag is set to avalue of 1 this component is protected (e.g. encrypted). When this flagis set to a value of 0 this component is not protected (e.g. encrypted).When not present the value of componentProtectedFlag attribute isinferred to be equal to 0. A meaning of a value of this field may bedifferently set depending on embodiments.

@atsc:componentId is an attribute that indicates the identifier of thiscomponent. The value of this attribute can be the same as the asset_idin the MP table corresponding to this component

@atsc:componentName is an attribute that indicates the human readablename of this component.

The proposed default values may vary depending on embodiments. The “use”column illustrated in the figure relates to each field. Here, M maydenote an essential field, O may denote an optional field, OD may denotean optional field having a default value, and CM may denote aconditional essential field. 0 . . . 1 to 0 . . . N may indicate thenumber of available fields.

Hereinafter, a description will be given of MPD for MMT.

The Media Presentation Description is an SLS metadata fragmentcorresponding to a linear service of a given duration defined by thebroadcaster (for example a single TV program, or the set of contiguouslinear TV programs over a period of time). The contents of the MPDprovide the resource identifiers for Segments and the context for theidentified resources within the Media Presentation. The data structureand semantics of the MPD can be according to the MPD defined by MPEGDASH.

In the present embodiment, an MPD delivered by an MMTP session describesRepresentations delivered over broadband, e.g. in the case of a hybridservice, or to support service continuity in handoff from broadcast tobroadband due to broadcast signal degradation (e.g. driving under amountain or through a tunnel).

Hereinafter, a description will be given of an MMT signaling message forMMT.

When MMTP sessions are used to carry a streaming service, MMT signalingmessages defined by MMT are delivered by MMTP packets according toSignaling Message Mode defined by MMT. The value of the packet_id fieldof MMTP packets carrying Service Layer Signaling Asset to ‘00’ exceptfor MMTP packets carrying MMT signaling messages specific to an Asset,which can be set to the same packet_id value as the MMTP packetscarrying the Asset. Identifiers referencing the appropriate Package foreach service are signaled by the USBD fragment as described above. MMTPackage Table (MPT) messages with matching MMT_package_id can bedelivered on the MMTP session signaled in the SLT. Each MMTP sessioncarries MMT signaling messages specific to its session or each assetdelivered by the MMTP session.

In other words, it is possible to access USBD of the MMTP session byspecifying an IP destination address/port number, etc. of a packethaving the SLS for a particular service in the SLT. As described in theforegoing, a packet ID of an MMTP packet carrying the SLS may bedesignated as a particular value such as 00, etc. It is possible toaccess an MPT message having a matched packet ID using theabove-described package IP information of USBD. As described below, theMPT message may be used to access each service component/asset.

The following MMTP messages can be delivered by the MMTP sessionsignaled in the SLT.

MMT Package Table (MPT) message: This message carries an MP (MMTPackage) table which contains the list of all Assets and their locationinformation as defined by MMT. If an Asset is delivered by a PLPdifferent from the current PLP delivering the MP table, the identifierof the PLP carrying the Asset can be provided in the MP table usingPhysical Layer Pipe Identifier Descriptor. The physical layer pipeidentifier descriptor will be described below.

MMT ATSC3 (MA3) message mmt_atsc3_message( ): This message carriessystem metadata specific for services including Service Layer Signalingas described above. mmt_atsc3_message( ) will be described below.

The following MMTP messages can be delivered by the MMTP sessionsignaled in the SLT, if required.

Media Presentation Information (MPI) message: This message carries anMPI table which contains the whole document or a subset of a document ofpresentation information. An MP table associated with the MPI table alsocan be delivered by this message.

Clock Relation Information (CRI) message: This message carries a CRItable which contains clock related information for the mapping betweenthe NTP timestamp and the MPEG-2 STC. According to a given embodiment,the CRI message may not be delivered through the MMTP session.

The following MMTP messages can be delivered by each MMTP sessioncarrying streaming content.

Hypothetical Receiver Buffer Model message: This message carriesinformation required by the receiver to manage its buffer.

Hypothetical Receiver Buffer Model Removal message: This message carriesinformation required by the receiver to manage its MMT de-capsulationbuffer.

Hereinafter, a description will be given of mmt_atsc3_message( )corresponding to one of MMT signaling messages. An MMT Signaling messagemmt_atsc3_message( ) is defined to deliver information specific toservices according to the present invention described above. Thesignaling message may include message ID, version, and/or length fieldscorresponding to basic fields of the MMT signaling message. A payload ofthe signaling message may include service ID information, content typeinformation, content version information, content compressioninformation and/or URI information. The content type information mayindicate a type of data included in the payload of the signalingmessage. The content version information may indicate a version of dataincluded in the payload, and the content compression information mayindicate a type of compression applied to the data. The URI informationmay have URI information related to content delivered by the message.

Hereinafter, a description will be given of the physical layer pipeidentifier descriptor.

The physical layer pipe identifier descriptor is a descriptor that canbe used as one of descriptors of the MP table described above. ThePhysical Layer Pipe Identifier Descriptor provides information about thePLP carrying an Asset. If an Asset is delivered by a PLP different fromthe current PLP delivering the MP table, the Physical Layer PipeIdentifier Descriptor can be used as an asset descriptor in theassociated MP table to identify the PLP carrying the Asset. The physicallayer pipe identifier descriptor may further include BSID information inaddition to PLP ID information. The BSID may be an ID of a broadcaststream that delivers an MMTP packet for an asset described by thedescriptor.

FIG. 8 illustrates a link layer protocol architecture according to anembodiment of the present invention.

Hereinafter, a link layer will be described.

The link layer is the layer between the physical layer and the networklayer, and transports the data from the network layer to the physicallayer at the sending side and transports the data from the physicallayer to the network layer at the receiving side. The purpose of thelink layer includes abstracting all input packet types into a singleformat for processing by the physical layer, ensuring flexibility andfuture extensibility for as yet undefined input types. In addition,processing within the link layer ensures that the input data can betransmitted in an efficient manner, for example by providing options tocompress redundant information in the headers of input packets. Theoperations of encapsulation, compression and so on are referred to asthe link layer protocol and packets created using this protocol arecalled link layer packets. The link layer may perform functions such aspacket encapsulation, overhead reduction and/or signaling transmission,etc.

Hereinafter, packet encapsulation will be described. Link Layer protocolallows encapsulation of any type of packet, including ones such as IPpackets and MPEG-2 TS. Using Link Layer protocol, the physical layerneed only process one single packet format, independent of the networklayer protocol type (here we consider MPEG-2 TS packet as a kind ofnetwork layer packet.) Each network layer packet or input packet istransformed into the payload of a generic link layer packet.Additionally, concatenation and segmentation can be performed in orderto use the physical layer resources efficiently when the input packetsizes are particularly small or large.

As described in the foregoing, segmentation may be used in packetencapsulation. When the network layer packet is too large to processeasily in the physical layer, the network layer packet is divided intotwo or more segments. The link layer packet header includes protocolfields to perform segmentation on the sending side and reassembly on thereceiving side. When the network layer packet is segmented, each segmentcan be encapsulated to link layer packet in the same order as originalposition in the network layer packet. Also each link layer packet whichincludes a segment of network layer packet can be transported to PHYlayer consequently.

As described in the foregoing, concatenation may be used in packetencapsulation. When the network layer packet is small enough for thepayload of a link layer packet to include several network layer packets,the link layer packet header includes protocol fields to performconcatenation. The concatenation is combining of multiple small sizednetwork layer packets into one payload. When the network layer packetsare concatenated, each network layer packet can be concatenated topayload of link layer packet in the same order as original input order.Also each packet which constructs a payload of link layer packet can bewhole packet, not a segment of packet.

Hereinafter, overhead reduction will be described. Use of the link layerprotocol can result in significant reduction in overhead for transportof data on the physical layer. The link layer protocol according to thepresent invention may provide IP overhead reduction and/or MPEG-2 TSoverhead reduction. In IP overhead reduction, IP packets have a fixedheader format, however some of the information which is needed in acommunication environment may be redundant in a broadcast environment.Link Layer protocol provides mechanisms to reduce the broadcast overheadby compressing headers of IP packets. In MPEG-2 TS overhead reduction,Link Layer protocol provides sync byte removal, null packet deletionand/or common header removal (compression). First, sync byte removalprovides an overhead reduction of one byte per TS packet, secondly anull packet deletion mechanism removes the 188 byte null TS packets in amanner that they can be re-inserted at the receiver and finally a commonheader removal mechanism.

For signaling transmission, in the link layer protocol, a particularformat for the signaling packet may be provided for link layersignaling, which will be described below.

In the illustrated link layer protocol architecture according to anembodiment of the present invention, Link Layer protocol takes as inputnetwork layer packets such as IPv4, MPEG-2 TS and so on as inputpackets. Future extension indicates other packet types and protocolwhich is also possible to be input in link layer. Link layer protocolalso specifies the format and signaling for any link layer signaling,including information about mapping to specific channel to the physicallayer. Figure also shows how ALP incorporates mechanisms to improve theefficiency of transmission, via various header compression and deletionalgorithms. In addition, the link layer protocol may basicallyencapsulate input packets.

FIG. 9 illustrates a structure of a base header of a link layer packetaccording to an embodiment of the present invention. Hereinafter, thestructure of the header will be described.

A link layer packet can include a header followed by the data payload.The header of a link layer packet can include a base header, and mayinclude an additional header depending on the control fields of the baseheader. The presence of an optional header is indicated from flag fieldsof the additional header. According to a given embodiment, a fieldindicating the presence of an additional header and an optional headermay be positioned in the base header.

Hereinafter, the structure of the base header will be described. Thebase header for link layer packet encapsulation has a hierarchicalstructure. The base header can be two bytes in length and is the minimumlength of the link layer packet header.

The illustrated base header according to the present embodiment mayinclude a Packet_Type field, a PC field and/or a length field. Accordingto a given embodiment, the base header may further include an HM fieldor an S/C field.

Packet Type field can be a 3-bit field that indicates the originalprotocol or packet type of the input data before encapsulation into alink layer packet. An IPv4 packet, a compressed IP packet, a link layersignaling packet, and other types of packets may have the base headerstructure and may be encapsulated. However, according to a givenembodiment, the MPEG-2 TS packet may have a different particularstructure, and may be encapsulated. When the value of Packet_Type is“000”, “001” “100” or “111”, that is the original data type of an ALPpacket is one of an IPv4 packet, a compressed IP packet, link layersignaling or extension packet. When the MPEG-2 TS packet isencapsulated, the value of Packet_Type can be “010”. Other values of thePacket_Type field may be reserved for future use.

Payload_Configuration (PC) field can be a 1-bit field that indicates theconfiguration of the payload. A value of 0 can indicate that the linklayer packet carries a single, whole input packet and the followingfield is the Header_Mode field. A value of 1 can indicate that the linklayer packet carries more than one input packet (concatenation) or apart of a large input packet (segmentation) and the following field isthe Segmentation_Concatenation field.

Header_Mode (HM) field can be a 1-bit field, when set to 0, that canindicate there is no additional header, and that the length of thepayload of the link layer packet is less than 2048 bytes. This value maybe varied depending on embodiments. A value of 1 can indicate that anadditional header for single packet defined below is present followingthe Length field. In this case, the length of the payload is larger than2047 bytes and/or optional features can be used (sub-streamidentification, header extension, etc.). This value may be varieddepending on embodiments. This field can be present only whenPayload_Configuration field of the link layer packet has a value of 0.

Segmentation_Concatenation (S/C) field can be a 1-bit field, when set to0, that can indicate that the payload carries a segment of an inputpacket and an Additional header for segmentation defined below ispresent following the Length field. A value of 1 can indicate that thepayload carries more than one complete input packet and an Additionalheader for concatenation defined below is present following the Lengthfield. This field can be present only when the value ofPayload_Configuration field of the ALP packet is 1.

Length field can be a 11-bit field that indicates the 11 leastsignificant bits (LSBs) of the length in bytes of payload carried by thelink layer packet. When there is a Length_MSB field in the followingadditional header, the Length field is concatenated with the Length_MSBfield, and is the LSB to provide the actual total length of the payload.The number of bits of the length field may be changed to another valuerather than 11 bits.

Following types of packet configuration are thus possible: a singlepacket without any additional header, a single packet with an additionalheader, a segmented packet and a concatenated packet. According to agiven embodiment, more packet configurations may be made through acombination of each additional header, an optional header, an additionalheader for signaling information to be described below, and anadditional header for time extension.

FIG. 10 illustrates a structure of an additional header of a link layerpacket according to an embodiment of the present invention.

Various types of additional headers may be present. Hereinafter, adescription will be given of an additional header for a single packet.

This additional header for single packet can be present when Header_Mode(HM)=“1”. The Header_Mode (HM) can be set to 1 when the length of thepayload of the link layer packet is larger than 2047 bytes or when theoptional fields are used. The additional header for single packet isshown in Figure (tsib10010).

Length_MSB field can be a 5-bit field that can indicate the mostsignificant bits (MSBs) of the total payload length in bytes in thecurrent link layer packet, and is concatenated with the Length fieldcontaining the 11 least significant bits (LSBs) to obtain the totalpayload length. The maximum length of the payload that can be signaledis therefore 65535 bytes. The number of bits of the length field may bechanged to another value rather than 11 bits. In addition, the number ofbits of the Length MSB field may be changed, and thus a maximumexpressible payload length may be changed. According to a givenembodiment, each length field may indicate a length of a whole linklayer packet rather than a payload.

SIF (Sub-stream Identifier Flag) field can be a 1-bit field that canindicate whether the sub-stream ID (SID) is present after the HEF fieldor not. When there is no SID in this link layer packet, SIF field can beset to 0. When there is a SID after HEF field in the link layer packet,SIF can be set to 1. The detail of SID is described below.

HEF (Header Extension Flag) field can be a 1-bit field that canindicate, when set to 1 additional header is present for futureextension. A value of 0 can indicate that this extension header is notpresent.

Hereinafter, a description will be given of an additional header whensegmentation is used.

This additional header (tsib10020) can be present whenSegmentation_Concatenation (S/C)=“0”. Segment_Sequence_Number can be a5-bit unsigned integer that can indicate the order of the correspondingsegment carried by the link layer packet. For the link layer packetwhich carries the first segment of an input packet, the value of thisfield can be set to 0x0. This field can be incremented by one with eachadditional segment belonging to the segmented input packet.

Last_Segment Indicator (LSI) can be a 1-bit field that can indicate,when set to 1, that the segment in this payload is the last one of inputpacket. A value of 0, can indicate that it is not last segment.

SIF (Sub-stream Identifier Flag) can be a 1-bit field that can indicatewhether the SID is present after the HEF field or not. When there is noSID in the link layer packet, SIF field can be set to 0. When there is aSID after the HEF field in the link layer packet, SIF can be set to 1.

HEF (Header Extension Flag) can be a This 1-bit field that can indicate,when set to 1, that the optional header extension is present after theadditional header for future extensions of the link layer header. Avalue of 0 can indicate that optional header extension is not present.

According to a given embodiment, a packet ID field may be additionallyprovided to indicate that each segment is generated from the same inputpacket. This field may be unnecessary and thus be omitted when segmentsare transmitted in order.

Hereinafter, a description will be given of an additional header whenconcatenation is used.

This additional header (tsib10030) can be present whenSegmentation_Concatenation (S/C)=“1”.

Length_MSB can be a 4-bit field that can indicate MSB bits of thepayload length in bytes in this link layer packet. The maximum length ofthe payload is 32767 bytes for concatenation. As described in theforegoing, a specific numeric value may be changed.

Count can be a field that can indicate the number of the packetsincluded in the link layer packet. The number of the packets included inthe link layer packet, 2 can be set to this field. So, its maximum valueof concatenated packets in a link layer packet is 9. A scheme in whichthe count field indicates the number may be varied depending onembodiments. That is, the numbers from 1 to 8 may be indicated.

HEF (Header Extension Flag) can be a 1-bit field that can indicate, whenset to 1 the optional header extension is present after the additionalheader for future extensions of the link layer header. A value of 0, canindicate extension header is not present.

Component_Length can be a is 12-bit length field that can indicate thelength in byte of each packet. Component Length fields are included inthe same order as the packets present in the payload except lastcomponent packet. The number of length field can be indicated by(Count+1). According to a given embodiment, length fields, the number ofwhich is the same as a value of the count field, may be present. When alink layer header consists of an odd number of Component_Length, fourstuffing bits can follow after the last Component_Length field. Thesebits can be set to 0. According to a given embodiment, a Componentlength field indicating a length of a last concatenated input packet maynot be present. In this case, the length of the last concatenated inputpacket may correspond to a length obtained by subtracting a sum ofvalues indicated by respective Component length fields from a wholepayload length.

Hereinafter, the optional header will be described.

As described in the foregoing, the optional header may be added to arear of the additional header. The optional header field can contain SIDand/or header extension. The SID is used to filter out specific packetstream in the link layer level. One example of SID is the role ofservice identifier in a link layer stream carrying multiple services.The mapping information between a service and the SID valuecorresponding to the service can be provided in the SLT, if applicable.The header extension contains extended field for future use. Receiverscan ignore any header extensions which they do not understand.

SID (Sub-stream Identifier) can be a 8-bit field that can indicate thesub stream identifier for the link layer packet. If there is optionalheader extension, SID present between additional header and optionalheader extension.

Header_Extension ( ) can include the fields defined below.

Extension_Type can be a 8-bit field that can indicate the type of theHeader_Extension ( ).

Extension_Length can be a 8-bit field that can indicate the length ofthe Header Extension ( ) in bytes counting from the next byte to thelast byte of the Header_Extension ( ).

Extension_Byte can be a byte representing the value of theHeader_Extension ( ).

FIG. 11 illustrates a structure of an additional header of a link layerpacket according to another embodiment of the present invention.

Hereinafter, a description will be given of an additional header forsignaling information.

How link layer signaling is incorporated into link layer packets are asfollows. Signaling packets are identified by when the Packet_Type fieldof the base header is equal to 100.

Figure (tsib11010) shows the structure of the link layer packetscontaining additional header for signaling information. In addition tothe link layer header, the link layer packet can consist of twoadditional parts, additional header for signaling information and theactual signaling data itself. The total length of the link layersignaling packet is shown in the link layer packet header.

The additional header for signaling information can include followingfields. According to a given embodiment, some fields may be omitted.

Signaling_Type can be a 8-bit field that can indicate the type ofsignaling.

Signaling_Type_Extension can be a 16-bit filed that can indicate theattribute of the signaling. Detail of this field can be defined insignaling specification.

Signaling_Version can be a 8-bit field that can indicate the version ofsignaling.

Signaling_Format can be a 2-bit field that can indicate the data formatof the signaling data. Here, a signaling format may refer to a dataformat such as a binary format, an XML format, etc.

Signaling_Encoding can be a 2-bit field that can specify theencoding/compression format. This field may indicate whether compressionis not performed and which type of compression is performed.

Hereinafter, a description will be given of an additional header forpacket type extension.

In order to provide a mechanism to allow an almost unlimited number ofadditional protocol and packet types to be carried by link layer in thefuture, the additional header is defined. Packet type extension can beused when Packet type is 111 in the base header as described above.Figure (tsib11020) shows the structure of the link layer packetscontaining additional header for type extension.

The additional header for type extension can include following fields.According to a given embodiment, some fields may be omitted.

extended type can be a 16-bit field that can indicate the protocol orpacket type of the input encapsulated in the link layer packet aspayload. This field can not be used for any protocol or packet typealready defined by Packet Type field.

FIG. 12 illustrates a header structure of a link layer packet for anMPEG-2 TS packet and an encapsulation process thereof according to anembodiment of the present invention.

Hereinafter, a description will be given of a format of the link layerpacket when the MPEG-2 TS packet is input as an input packet.

In this case, the Packet_Type field of the base header is equal to 010.Multiple TS packets can be encapsulated within each link layer packet.The number of TS packets is signaled via the NUMTS field. In this case,as described in the foregoing, a particular link layer packet headerformat may be used.

Link layer provides overhead reduction mechanisms for MPEG-2 TS toenhance the transmission efficiency. The sync byte (0x47) of each TSpacket can be deleted. The option to delete NULL packets and similar TSheaders is also provided.

In order to avoid unnecessary transmission overhead, TS null packets(PID=0x1FFF) may be removed. Deleted null packets can be recovered inreceiver side using DNP field. The DNP field indicates the count ofdeleted null packets. Null packet deletion mechanism using DNP field isdescribed below.

In order to achieve more transmission efficiency, similar header ofMPEG-2 TS packets can be removed. When two or more successive TS packetshave sequentially increased continuity counter fields and other headerfields are the same, the header is sent once at the first packet and theother headers are deleted. HDM field can indicate whether the headerdeletion is performed or not. Detailed procedure of common TS headerdeletion is described below.

When all three overhead reduction mechanisms are performed, overheadreduction can be performed in sequence of sync removal, null packetdeletion, and common header deletion. According to a given embodiment, aperformance order of respective mechanisms may be changed. In addition,some mechanisms may be omitted according to a given embodiment.

The overall structure of the link layer packet header when using MPEG-2TS packet encapsulation is depicted in Figure (tsib12010).

Hereinafter, a description will be given of each illustrated field.Packet_Type can be a 3-bit field that can indicate the protocol type ofinput packet as describe above. For MPEG-2 TS packet encapsulation, thisfield can always be set to 010.

NUMTS (Number of TS packets) can be a 4-bit field that can indicate thenumber of TS packets in the payload of this link layer packet. A maximumof 16 TS packets can be supported in one link layer packet. The value ofNUMTS=0 can indicate that 16 TS packets are carried by the payload ofthe link layer packet. For all other values of NUMTS, the same number ofTS packets are recognized, e.g. NUMTS=0001 means one TS packet iscarried.

AHF (Additional Header Flag) can be a field that can indicate whetherthe additional header is present of not. A value of 0 indicates thatthere is no additional header. A value of 1 indicates that an additionalheader of length 1-byte is present following the base header. If null TSpackets are deleted or TS header compression is applied this field canbe set to 1. The additional header for TS packet encapsulation consistsof the following two fields and is present only when the value of AHF inthis link layer packet is set to 1.

HDM (Header Deletion Mode) can be a 1-bit field that indicates whetherTS header deletion can be applied to this link layer packet. A value of1 indicates that TS header deletion can be applied. A value of “0”indicates that the TS header deletion method is not applied to this linklayer packet.

DNP (Deleted Null Packets) can be a 7-bit field that indicates thenumber of deleted null TS packets prior to this link layer packet. Amaximum of 128 null TS packets can be deleted. When HDM=0 the value ofDNP=0 can indicate that 128 null packets are deleted. When HDM=1 thevalue of DNP=0 can indicate that no null packets are deleted. For allother values of DNP, the same number of null packets are recognized,e.g. DNP=5 means 5 null packets are deleted.

The number of bits of each field described above may be changed.According to the changed number of bits, a minimum/maximum value of avalue indicated by the field may be changed. These numbers may bechanged by a designer.

Hereinafter, SYNC byte removal will be described.

When encapsulating TS packets into the payload of a link layer packet,the SYNC byte (0x47) from the start of each TS packet can be deleted.Hence the length of the MPEG2-TS packet encapsulated in the payload ofthe link layer packet is always of length 187 bytes (instead of 188bytes originally).

Hereinafter, null packet deletion will be described.

Transport Stream rules require that bit rates at the output of atransmitter's multiplexer and at the input of the receiver'sde-multiplexer are constant in time and the end-to-end delay is alsoconstant. For some Transport Stream input signals, null packets may bepresent in order to accommodate variable bitrate services in a constantbitrate stream. In this case, in order to avoid unnecessary transmissionoverhead, TS null packets (that is TS packets with PID=0x1FFF) may beremoved. The process is carried-out in a way that the removed nullpackets can be re-inserted in the receiver in the exact place where theywere originally, thus guaranteeing constant bitrate and avoiding theneed for PCR time stamp updating.

Before generation of a link layer packet, a counter called DNP (DeletedNull-Packets) can first be reset to zero and then incremented for eachdeleted null packet preceding the first non-null TS packet to beencapsulated into the payload of the current link layer packet. Then agroup of consecutive useful TS packets is encapsulated into the payloadof the current link layer packet and the value of each field in itsheader can be determined. After the generated link layer packet isinjected to the physical layer, the DNP is reset to zero. When DNPreaches its maximum allowed value, if the next packet is also a nullpacket, this null packet is kept as a useful packet and encapsulatedinto the payload of the next link layer packet. Each link layer packetcan contain at least one useful TS packet in its payload.

Hereinafter, TS packet header deletion will be described. TS packetheader deletion may be referred to as TS packet header compression.

When two or more successive TS packets have sequentially increasedcontinuity counter fields and other header fields are the same, theheader is sent once at the first packet and the other headers aredeleted. When the duplicated MPEG-2 TS packets are included in two ormore successive TS packets, header deletion can not be applied intransmitter side. HDM field can indicate whether the header deletion isperformed or not. When TS header deletion is performed, HDM can be setto 1. In the receiver side, using the first packet header, the deletedpacket headers are recovered, and the continuity counter is restored byincreasing it in order from that of the first header.

An example tsib12020 illustrated in the figure is an example of aprocess in which an input stream of a TS packet is encapsulated into alink layer packet. First, a TS stream including TS packets having SYNCbyte (0x47) may be input. First, sync bytes may be deleted through async byte deletion process. In this example, it is presumed that nullpacket deletion is not performed.

Here, it is presumed that packet headers of eight TS packets have thesame field values except for CC, that is, a continuity counter fieldvalue. In this case, TS packet deletion/compression may be performed.Seven remaining TS packet headers are deleted except for a first TSpacket header corresponding to CC=1. The processed TS packets may beencapsulated into a payload of the link layer packet.

In a completed link layer packet, a Packet_Type field corresponds to acase in which TS packets are input, and thus may have a value of 010. ANUMTS field may indicate the number of encapsulated TS packets. An AHFfield may be set to 1 to indicate the presence of an additional headersince packet header deletion is performed. An HDM field may be set to 1since header deletion is performed. DNP may be set to 0 since nullpacket deletion is not performed.

FIG. 13 illustrates an example of adaptation modes in IP headercompression according to an embodiment of the present invention(transmitting side).

Hereinafter, IP header compression will be described.

In the link layer, IP header compression/decompression scheme can beprovided. IP header compression can include two parts: headercompressor/decompressor and adaptation module. The header compressionscheme can be based on the Robust Header Compression (ROHC). Inaddition, for broadcasting usage, adaptation function is added.

In the transmitter side, ROHC Compressor reduces the size of header foreach packet. Then, Adaptation module extracts context information andbuilds signaling information from each packet stream. In the receiverside, adaptation module parses the signaling information associated withthe received packet stream and attaches context information to thereceived packet stream. ROHC decompressor reconstructs the original IPpacket by recovering the packet header.

The header compression scheme can be based on the RoHC as describedabove. In particular, in the present system, an RoHC framework canoperate in a unidirectional mode (U mode) of the RoHC. In addition, inthe present system, it is possible to use an RoHC UDP header compressionprofile which is identified by a profile identifier of 0x0002.

Hereinafter, adaptation will be described.

In case of transmission through the unidirectional link, if a receiverhas no information of context, decompressor cannot recover the receivedpacket header until receiving full context. This may cause channelchange delay and turn on delay. For this reason, context information andconfiguration parameters between compressor and decompressor can bealways sent with packet flow.

The Adaptation function provides out-of-band transmission of theconfiguration parameters and context information. Out-of-bandtransmission can be done through the link layer signaling. Therefore,the Adaptation function is used to reduce the channel change delay anddecompression error due to loss of context information.

Hereinafter, extraction of context information will be described.

Context information may be extracted using various schemes according toadaptation mode. In the present invention, three examples will bedescribed below. The scope of the present invention is not restricted tothe examples of the adaptation mode to be described below. Here, theadaptation mode may be referred to as a context extraction mode.

Adaptation Mode 1 (not illustrated) may be a mode in which no additionaloperation is applied to a basic RoHC packet stream. In other words, theadaptation module may operate as a buffer in this mode. Therefore, inthis mode, context information may not be included in link layersignaling.

In Adaptation Mode 2 (tsib13010), the adaptation module can detect theIR packet from ROHC packet flow and extract the context information(static chain). After extracting the context information, each IR packetcan be converted to an IR-DYN packet. The converted IR-DYN packet can beincluded and transmitted inside the ROHC packet flow in the same orderas IR packet, replacing the original packet.

In Adaptation Mode 3 (tsib13020), the adaptation module can detect theIR and IR-DYN packet from ROHC packet flow and extract the contextinformation. The static chain and dynamic chain can be extracted from IRpacket and dynamic chain can be extracted from IR-DYN packet. Afterextracting the context information, each IR and IR-DYN packet can beconverted to a compressed packet. The compressed packet format can bethe same with the next packet of IR or IR-DYN packet. The convertedcompressed packet can be included and transmitted inside the ROHC packetflow in the same order as IR or IR-DYN packet, replacing the originalpacket.

Signaling (Context) information can be encapsulated based ontransmission structure. For example, context information can beencapsulated to the link layer signaling. In this case, the packet typevalue can be set to ‘100’.

In the above-described Adaptation Modes 2 and 3, a link layer packet forcontext information may have a packet type field value of 100. Inaddition, a link layer packet for compressed IP packets may have apacket type field value of 001. The values indicate that each of thesignaling information and the compressed IP packets are included in thelink layer packet as described above.

Hereinafter, a description will be given of a method of transmitting theextracted context information.

The extracted context information can be transmitted separately fromROHC packet flow, with signaling data through specific physical datapath. The transmission of context depends on the configuration of thephysical layer path. The context information can be sent with other linklayer signaling through the signaling data pipe.

In other words, the link layer packet having the context information maybe transmitted through a signaling PLP together with link layer packetshaving other link layer signaling information (Packet_Type=100).Compressed IP packets from which context information is extracted may betransmitted through a general PLP (Packet_Type=001). Here, depending onembodiments, the signaling PLP may refer to an L1 signaling path. Inaddition, depending on embodiments, the signaling PLP may not beseparated from the general PLP, and may refer to a particular andgeneral PLP through which the signaling information is transmitted.

At a receiving side, prior to reception of a packet stream, a receivermay need to acquire signaling information. When receiver decodes initialPLP to acquire the signaling information, the context signaling can bealso received. After the signaling acquisition is done, the PLP toreceive packet stream can be selected. In other words, the receiver mayacquire the signaling information including the context information byselecting the initial PLP. Here, the initial PLP may be theabove-described signaling PLP. Thereafter, the receiver may select a PLPfor acquiring a packet stream. In this way, the context information maybe acquired prior to reception of the packet stream.

After the PLP for acquiring the packet stream is selected, theadaptation module can detect IR-DYN packet form received packet flow.Then, the adaptation module parses the static chain from the contextinformation in the signaling data. This is similar to receiving the IRpacket. For the same context identifier, IR-DYN packet can be recoveredto IR packet. Recovered ROHC packet flow can be sent to ROHCdecompressor. Thereafter, decompression may be started.

FIG. 14 illustrates a link mapping table (LMT) and an RoHC-U descriptiontable according to an embodiment of the present invention.

Hereinafter, link layer signaling will be described.

Generally, link layer signaling is operates under IP level. In thereceiver side, link layer signaling can be obtained earlier than IPlevel signaling such as Service List Table (SLT) and Service LayerSignaling (SLS). Therefore, link layer signaling can be obtained beforesession establishment.

For link layer signaling, there can be two kinds of signaling accordinginput path: internal link layer signaling and external link layersignaling. The internal link layer signaling is generated in link layerat transmitter side. And the link layer takes the signaling fromexternal module or protocol. This kind of signaling information isconsidered as external link layer signaling. If some signaling need tobe obtained prior to IP level signaling, external signaling istransmitted in format of link layer packet.

The link layer signaling can be encapsulated into link layer packet asdescribed above. The link layer packets can carry any format of linklayer signaling, including binary and XML. The same signalinginformation may not be transmitted in different formats for the linklayer signaling.

Internal link layer signaling may include signaling information for linkmapping. The Link Mapping Table (LMT) provides a list of upper layersessions carried in a PLP. The LMT also provides addition informationfor processing the link layer packets carrying the upper layer sessionsin the link layer.

An example of the LMT (tsib14010) according to the present invention isillustrated.

signaling_type can be an 8-bit unsigned integer field that indicates thetype of signaling carried by this table. The value of signaling_typefield for Link Mapping Table (LMT) can be set to 0x01.

PLP_ID can be an 8-bit field that indicates the PLP corresponding tothis table.

num_session can be an 8-bit unsigned integer field that provides thenumber of upper layer sessions carried in the PLP identified by theabove PLP_ID field. When the value of signaling_type field is 0x01, thisfield can indicate the number of UDP/IP sessions in the PLP.

src_IP_add can be a 32-bit unsigned integer field that contains thesource IP address of an upper layer session carried in the PLPidentified by the PLP_ID field.

dst_IP_add can be a 32-bit unsigned integer field that contains thedestination IP address of an upper layer session carried in the PLPidentified by the PLP_ID field.

src_UDP_port can be a 16-bit unsigned integer field that represents thesource UDP port number of an upper layer session carried in the PLPidentified by the PLP_ID field.

dst_UDP_port can be a 16-bit unsigned integer field that represents thedestination UDP port number of an upper layer session carried in the PLPidentified by the PLP_ID field.

SID_flag can be a 1-bit Boolean field that indicates whether the linklayer packet carrying the upper layer session identified by above 4fields, Src_IP_add, Dst_IP_add, Src_UDP_Port and Dst_UDP_Port, has anSID field in its optional header. When the value of this field is set to0, the link layer packet carrying the upper layer session may not havean SID field in its optional header. When the value of this field is setto 1, the link layer packet carrying the upper layer session can have anSID field in its optional header and the value the SID field can be sameas the following SID field in this table.

compressed_flag can be a 1-bit Boolean field that indicates whether theheader compression is applied the link layer packets carrying the upperlayer session identified by above 4 fields, Src_IP_add, Dst_IP_add,Src_UDP_Port and Dst_UDP_Port. When the value of this field is set to 0,the link layer packet carrying the upper layer session may have a valueof 0x00 of Packet_Type field in its base header. When the value of thisfield is set to 1, the link layer packet carrying the upper layersession may have a value of 0x01 of Packet_Type field in its base headerand the Context_ID field can be present.

SID can be an 8-bit unsigned integer field that indicates sub-streamidentifier for the link layer packets carrying the upper layer sessionidentified by above 4 fields, Src_IP_add, Dst_IP_add, Src_UDP_Port andDst_UDP_Port. This field can be present when the value of SID_flag isequal to 1.

context_id can be an 8-bit field that provides a reference for thecontext id (CID) provided in the ROHC-U description table. This fieldcan be present when the value of compressed_flag is equal to 1.

An example of the RoHC-U description table (tsib14020) according to thepresent invention is illustrated. As described in the foregoing, theRoHC-U adaptation module may generate information related to headercompression.

signaling_type can be an 8-bit field that indicates the type ofsignaling carried by this table. The value of signaling_type field forROHC-U description table (RDT) can be set to “0x02”.

PLP_ID can be an 8-bit field that indicates the PLP corresponding tothis table.

context_id can be an 8-bit field that indicates the context id (CID) ofthe compressed IP stream. In this system, 8-bit CID can be used forlarge CID.

context_profile can be an 8-bit field that indicates the range ofprotocols used to compress the stream. This field can be omitted.

adaptation_mode can be a 2-bit field that indicates the mode ofadaptation module in this PLP. Adaptation modes have been describedabove.

context_config can be a 2-bit field that indicates the combination ofthe context information. If there is no context information in thistable, this field may be set to ‘0x0’. If the static_chain( ) ordynamic_chain( ) byte is included in this table, this field may be setto ‘0x01’ or ‘0x02’ respectively. If both of the static_chain( ) anddynamic_chain( ) byte are included in this table, this field may be setto ‘0x03’.

context length can be an 8-bit field that indicates the length of thestatic chain byte sequence. This field can be omitted.

static_chain byte ( ) can be a field that conveys the static informationused to initialize the ROHC-U decompressor. The size and structure ofthis field depend on the context profile.

dynamic_chain_byte ( ) can be a field that conveys the dynamicinformation used to initialize the ROHC-U decompressor. The size andstructure of this field depend on the context profile.

The static_chain byte can be defined as sub-header information of IRpacket. The dynamic_chain byte can be defined as sub-header informationof IR packet and IR-DYN packet.

FIG. 15 illustrates a structure of a link layer on a transmitter sideaccording to an embodiment of the present invention.

The present embodiment presumes that an IP packet is processed. From afunctional point of view, the link layer on the transmitter side maybroadly include a link layer signaling part in which signalinginformation is processed, an overhead reduction part, and/or anencapsulation part. In addition, the link layer on the transmitter sidemay include a scheduler for controlling and scheduling an overalloperation of the link layer and/or input and output parts of the linklayer.

First, signaling information of an upper layer and/or a system parametertsib15010 may be delivered to the link layer. In addition, an IP streamincluding IP packets may be delivered to the link layer from an IP layertsib15110.

As described above, the scheduler tsib15020 may determine and controloperations of several modules included in the link layer. The deliveredsignaling information and/or system parameter tsib15010 may be filtereror used by the scheduler tsib15020. Information, which corresponds to apart of the delivered signaling information and/or system parametertsib15010, necessary for a receiver may be delivered to the link layersignaling part. In addition, information, which corresponds to a part ofthe signaling information, necessary for an operation of the link layermay be delivered to an overhead reduction controller tsib15120 or anencapsulation controller tsib15180.

The link layer signaling part may collect information to be transmittedas a signal in a physical layer, and convert/configure the informationin a form suitable for transmission. The link layer signaling part mayinclude a signaling manager tsib15030, a signaling formatter tsib15040,and/or a buffer for channels tsib15050.

The signaling manager tsib15030 may receive signaling informationdelivered from the scheduler tsib15020 and/or signaling (and/or context)information delivered from the overhead reduction part. The signalingmanager tsib15030 may determine a path for transmission of the signalinginformation for delivered data. The signaling information may bedelivered through the path determined by the signaling managertsib15030. As described in the foregoing, signaling information to betransmitted through a divided channel such as the FIC, the EAS, etc. maybe delivered to the signaling formatter tsib15040, and other signalinginformation may be delivered to an encapsulation buffer tsib15070.

The signaling formatter tsib15040 may format related signalinginformation in a form suitable for each divided channel such thatsignaling information may be transmitted through a separately dividedchannel. As described in the foregoing, the physical layer may includeseparate physically/logically divided channels. The divided channels maybe used to transmit FIC signaling information or EAS-relatedinformation. The FIC or EAS-related information may be sorted by thesignaling manager tsib15030, and input to the signaling formattertsib15040. The signaling formatter tsib15040 may format the informationbased on each separate channel. When the physical layer is designed totransmit particular signaling information through a separately dividedchannel other than the FIC and the EAS, a signaling formatter for theparticular signaling information may be additionally provided. Throughthis scheme, the link layer may be compatible with various physicallayers.

The buffer for channels tsib15050 may deliver the signaling informationreceived from the signaling formatter tsib15040 to separate dedicatedchannels tsib15060. The number and content of the separate channels mayvary depending on embodiments.

As described in the foregoing, the signaling manager tsib15030 maydeliver signaling information, which is not delivered to a particularchannel, to the encapsulation buffer tsib15070. The encapsulation buffertsib15070 may function as a buffer that receives the signalinginformation which is not delivered to the particular channel.

An encapsulation block for signaling information tsib15080 mayencapsulate the signaling information which is not delivered to theparticular channel. A transmission buffer tsib15090 may function as abuffer that delivers the encapsulated signaling information to a DP forsignaling information tsib15100. Here, the DP for signaling informationtsib15100 may refer to the above-described PLS region.

The overhead reduction part may allow efficient transmission by removingoverhead of packets delivered to the link layer. It is possible toconfigure overhead reduction parts corresponding to the number of IPstreams input to the link layer.

An overhead reduction buffer tsib15130 may receive an IP packetdelivered from an upper layer. The received IP packet may be input tothe overhead reduction part through the overhead reduction buffertsib15130.

An overhead reduction controller tsib15120 may determine whether toperform overhead reduction on a packet stream input to the overheadreduction buffer tsib15130. The overhead reduction controller tsib15120may determine whether to perform overhead reduction for each packetstream. When overhead reduction is performed on a packet stream, packetsmay be delivered to a robust header compression (RoHC) compressortsib15140 to perform overhead reduction. When overhead reduction is notperformed on a packet stream, packets may be delivered to theencapsulation part to perform encapsulation without overhead reduction.Whether to perform overhead reduction of packets may be determined basedon the signaling information tsib15010 delivered to the link layer. Thesignaling information may be delivered to the encapsulation controllertsib15180 by the scheduler tsib15020.

The RoHC compressor tsib15140 may perform overhead reduction on a packetstream. The RoHC compressor tsib15140 may perform an operation ofcompressing a header of a packet. Various schemes may be used foroverhead reduction. Overhead reduction may be performed using a schemeproposed by the present invention. The present invention presumes an IPstream, and thus an expression “RoHC compressor” is used. However, thename may be changed depending on embodiments. The operation is notrestricted to compression of the IP stream, and overhead reduction ofall types of packets may be performed by the RoHC compressor tsib15140.

A packet stream configuration block tsib15150 may separate informationto be transmitted to a signaling region and information to betransmitted to a packet stream from IP packets having compressedheaders. The information to be transmitted to the packet stream mayrefer to information to be transmitted to a DP region. The informationto be transmitted to the signaling region may be delivered to asignaling and/or context controller tsib15160.

The information to be transmitted to the packet stream may betransmitted to the encapsulation part.

The signaling and/or context controller tsib15160 may collect signalingand/or context information and deliver the signaling and/or contextinformation to the signaling manager in order to transmit the signalingand/or context information to the signaling region.

The encapsulation part may perform an operation of encapsulating packetsin a form suitable for a delivery to the physical layer. It is possibleto configure encapsulation parts corresponding to the number of IPstreams.

An encapsulation buffer tsib15170 may receive a packet stream forencapsulation. Packets subjected to overhead reduction may be receivedwhen overhead reduction is performed, and an input IP packet may bereceived without change when overhead reduction is not performed.

An encapsulation controller tsib15180 may determine whether toencapsulate an input packet stream. When encapsulation is performed, thepacket stream may be delivered to a segmentation/concatenation blocktsib15190. When encapsulation is not performed, the packet stream may bedelivered to a transmission buffer tsib15230. Whether to encapsulatepackets may be determined based on the signaling information tsib15010delivered to the link layer. The signaling information may be deliveredto the encapsulation controller tsib15180 by the scheduler tsib15020.

In the segmentation/concatenation block tsib15190, the above-describedsegmentation or concatenation operation may be performed on packets. Inother words, when an input IP packet is longer than a link layer packetcorresponding to an output of the link layer, one IP packet may besegmented into several segments to configure a plurality of link layerpacket payloads. On the other hand, when an input IP packet is shorterthan a link layer packet corresponding to an output of the link layer,several IP packets may be concatenated to configure one link layerpacket payload.

A packet configuration table tsib15200 may have configurationinformation of a segmented and/or concatenated link layer packet. Atransmitter and a receiver may have the same information in the packetconfiguration table tsib15200. The transmitter and the receiver mayrefer to the information of the packet configuration table tsib15200. Anindex value of the information of the packet configuration tabletsib15200 may be included in a header of the link layer packet.

A link layer header information block tsib15210 may collect headerinformation generated in an encapsulation process. In addition, the linklayer header information block tsib15210 may collect header informationincluded in the packet configuration table tsib15200. The link layerheader information block tsib15210 may configure header informationaccording to a header structure of the link layer packet.

A header attachment block tsib15220 may add a header to a payload of asegmented and/or concatenated link layer packet. The transmission buffertsib15230 may function as a buffer to deliver the link layer packet to aDP tsib15240 of the physical layer.

The respective blocks, modules, or parts may be configured as onemodule/protocol or a plurality of modules/protocols in the link layer.

FIG. 16 illustrates a structure of a link layer on a receiver sideaccording to an embodiment of the present invention.

The present embodiment presumes that an IP packet is processed. From afunctional point of view, the link layer on the receiver side maybroadly include a link layer signaling part in which signalinginformation is processed, an overhead processing part, and/or adecapsulation part. In addition, the link layer on the receiver side mayinclude a scheduler for controlling and scheduling overall operation ofthe link layer and/or input and output parts of the link layer.

First, information received through a physical layer may be delivered tothe link layer. The link layer may process the information, restore anoriginal state before being processed at a transmitter side, and thendeliver the information to an upper layer. In the present embodiment,the upper layer may be an IP layer.

Information, which is separated in the physical layer and deliveredthrough a particular channel tsib16030, may be delivered to a link layersignaling part. The link layer signaling part may determine signalinginformation received from the physical layer, and deliver the determinedsignaling information to each part of the link layer.

A buffer for channels tsib16040 may function as a buffer that receivessignaling information transmitted through particular channels. Asdescribed in the foregoing, when physically/logically divided separatechannels are present in the physical layer, it is possible to receivesignaling information transmitted through the channels. When theinformation received from the separate channels is segmented, thesegmented information may be stored until complete information isconfigured.

A signaling decoder/parser tsib16050 may verify a format of thesignaling information received through the particular channel, andextract information to be used in the link layer. When the signalinginformation received through the particular channel is encoded, decodingmay be performed. In addition, according to a given embodiment, it ispossible to verify integrity, etc. of the signaling information.

A signaling manager tsib16060 may integrate signaling informationreceived through several paths. Signaling information received through aDP for signaling tsib16070 to be described below may be integrated inthe signaling manager tsib16060. The signaling manager tsib16060 maydeliver signaling information necessary for each part in the link layer.For example, the signaling manager tsib16060 may deliver contextinformation, etc. for recovery of a packet to the overhead processingpart. In addition, the signaling manager tsib16060 may deliver signalinginformation for control to a scheduler tsib16020.

General signaling information, which is not received through a separateparticular channel, may be received through the DP for signalingtsib16070. Here, the DP for signaling may refer to PLS, L1, etc. Here,the DP may be referred to as a PLP. A reception buffer tsib16080 mayfunction as a buffer that receives signaling information delivered fromthe DP for signaling. In a decapsulation block for signaling informationtsib16090, the received signaling information may be decapsulated. Thedecapsulated signaling information may be delivered to the signalingmanager tsib16060 through a decapsulation buffer tsib16100. As describedin the foregoing, the signaling manager tsib16060 may collate signalinginformation, and deliver the collated signaling information to anecessary part in the link layer.

The scheduler tsib16020 may determine and control operations of severalmodules included in the link layer. The scheduler tsib16020 may controleach part of the link layer using receiver information tsib16010 and/orinformation delivered from the signaling manager tsib16060. In addition,the scheduler tsib16020 may determine an operation mode, etc. of eachpart. Here, the receiver information tsib16010 may refer to informationpreviously stored in the receiver. The scheduler tsib16020 may useinformation changed by a user such as channel switching, etc. to performa control operation.

The decapsulation part may filter a packet received from a DP tsib16110of the physical layer, and separate a packet according to a type of thepacket. It is possible to configure decapsulation parts corresponding tothe number of DPs that can be simultaneously decoded in the physicallayer.

The decapsulation buffer tsib16100 may function as a buffer thatreceives a packet stream from the physical layer to performdecapsulation. A decapsulation controller tsib16130 may determinewhether to decapsulate an input packet stream. When decapsulation isperformed, the packet stream may be delivered to a link layer headerparser tsib16140. When decapsulation is not performed, the packet streammay be delivered to an output buffer tsib16220. The signalinginformation received from the scheduler tsib16020 may be used todetermine whether to perform decapsulation.

The link layer header parser tsib16140 may identify a header of thedelivered link layer packet. It is possible to identify a configurationof an IP packet included in a payload of the link layer packet byidentifying the header. For example, the IP packet may be segmented orconcatenated.

A packet configuration table tsib16150 may include payload informationof segmented and/or concatenated link layer packets. The transmitter andthe receiver may have the same information in the packet configurationtable tsib16150. The transmitter and the receiver may refer to theinformation of the packet configuration table tsib16150. It is possibleto find a value necessary for reassembly based on index informationincluded in the link layer packet.

A reassembly block tsib16160 may configure payloads of the segmentedand/or concatenated link layer packets as packets of an original IPstream. Segments may be collected and reconfigured as one IP packet, orconcatenated packets may be separated and reconfigured as a plurality ofIP packet streams. Recombined IP packets may be delivered to theoverhead processing part.

The overhead processing part may perform an operation of restoring apacket subjected to overhead reduction to an original packet as areverse operation of overhead reduction performed in the transmitter.This operation may be referred to as overhead processing. It is possibleto configure overhead processing parts corresponding to the number ofDPs that can be simultaneously decoded in the physical layer.

A packet recovery buffer tsib16170 may function as a buffer thatreceives a decapsulated RoHC packet or IP packet to perform overheadprocessing.

An overhead controller tsib16180 may determine whether to recover and/ordecompress the decapsulated packet. When recovery and/or decompressionare performed, the packet may be delivered to a packet stream recoveryblock tsib16190. When recovery and/or decompression are not performed,the packet may be delivered to the output buffer tsib16220. Whether toperform recovery and/or decompression may be determined based on thesignaling information delivered by the scheduler tsib16020.

The packet stream recovery block tsib16190 may perform an operation ofintegrating a packet stream separated from the transmitter with contextinformation of the packet stream. This operation may be a process ofrestoring a packet stream such that an RoHC decompressor tsib16210 canperform processing. In this process, it is possible to receive signalinginformation and/or context information from a signaling and/or contextcontroller tsib16200. The signaling and/or context controller tsib16200may determine signaling information delivered from the transmitter, anddeliver the signaling information to the packet stream recovery blocktsib16190 such that the signaling information may be mapped to a streamcorresponding to a context ID.

The RoHC decompressor tsib16210 may restore headers of packets of thepacket stream. The packets of the packet stream may be restored to formsof original IP packets through restoration of the headers. In otherwords, the RoHC decompressor tsib16210 may perform overhead processing.

The output buffer tsib16220 may function as a buffer before an outputstream is delivered to an IP layer tsib16230.

The link layers of the transmitter and the receiver proposed in thepresent invention may include the blocks or modules described above. Inthis way, the link layer may independently operate irrespective of anupper layer and a lower layer, overhead reduction may be efficientlyperformed, and a supportable function according to an upper/lower layermay be easily defined/added/deleted.

FIG. 17 illustrates a configuration of signaling transmission through alink layer according to an embodiment of the present invention(transmitting/receiving sides).

In the present invention, a plurality of service providers(broadcasters) may provide services within one frequency band. Inaddition, a service provider may provide a plurality of services, andone service may include one or more components. It can be consideredthat the user receives content using a service as a unit.

The present invention presumes that a transmission protocol based on aplurality of sessions is used to support an IP hybrid broadcast.Signaling information delivered through a signaling path may bedetermined based on a transmission configuration of each protocol.Various names may be applied to respective protocols according to agiven embodiment.

In the illustrated data configuration tsib17010 on the transmittingside, service providers (broadcasters) may provide a plurality ofservices (Service #1, #2, . . . ). In general, a signal for a servicemay be transmitted through a general transmission session (signaling C).However, the signal may be transmitted through a particular session(dedicated session) according to a given embodiment (signaling B).

Service data and service signaling information may be encapsulatedaccording to a transmission protocol. According to a given embodiment,an IP/UDP layer may be used. According to a given embodiment, a signalin the IP/UDP layer (signaling A) may be additionally provided. Thissignaling may be omitted.

Data processed using the IP/UDP may be input to the link layer. Asdescribed in the foregoing, overhead reduction and/or encapsulation maybe performed in the link layer. Here, link layer signaling may beadditionally provided. Link layer signaling may include a systemparameter, etc. Link layer signaling has been described above.

The service data and the signaling information subjected to the aboveprocess may be processed through PLPs in a physical layer. Here, a PLPmay be referred to as a DP. The example illustrated in the figurepresumes a case in which a base DP/PLP is used. However, depending onembodiments, transmission may be performed using only a general DP/PLPwithout the base DP/PLP.

In the example illustrated in the figure, a particular channel(dedicated channel) such as an FIC, an EAC, etc. is used. A signaldelivered through the FIC may be referred to as a fast information table(FIT), and a signal delivered through the EAC may be referred to as anemergency alert table (EAT). The FIT may be identical to theabove-described SLT. The particular channels may not be used dependingon embodiments. When the particular channel (dedicated channel) is notconfigured, the FIT and the EAT may be transmitted using a general linklayer signaling transmission scheme, or transmitted using a PLP via theIP/UDP as other service data.

According to a given embodiment, system parameters may include atransmitter-related parameter, a service provider-related parameter,etc. Link layer signaling may include IP header compression-relatedcontext information and/or identification information of data to whichthe context is applied. Signaling of an upper layer may include an IPaddress, a UDP number, service/component information, emergencyalert-related information, an IP/UDP address for service signaling, asession ID, etc. Detailed examples thereof have been described above.

In the illustrated data configuration tsib17020 on the receiving side,the receiver may decode only a PLP for a corresponding service usingsignaling information without having to decode all PLPs.

First, when the user selects or changes a service desired to bereceived, the receiver may be tuned to a corresponding frequency and mayread receiver information related to a corresponding channel stored in aDB, etc. The information stored in the DB, etc. of the receiver may beconfigured by reading an SLT at the time of initial channel scan.

After receiving the SLT and the information about the correspondingchannel, information previously stored in the DB is updated, andinformation about a transmission path of the service selected by theuser and information about a path, through which component informationis acquired or a signal necessary to acquire the information istransmitted, are acquired. When the information is not determined to bechanged using version information of the SLT, decoding or parsing may beomitted.

The receiver may verify whether SLT information is included in a PLP byparsing physical signaling of the PLP in a corresponding broadcaststream (not illustrated), which may be indicated through a particularfield of physical signaling. It is possible to access a position atwhich a service layer signal of a particular service is transmitted byaccessing the SLT information. The service layer signal may beencapsulated into the IP/UDP and delivered through a transmissionsession. It is possible to acquire information about a componentincluded in the service using this service layer signaling. A specificSLT-SLS configuration is as described above.

In other words, it is possible to acquire transmission path information,for receiving upper layer signaling information (service signalinginformation) necessary to receive the service, corresponding to one ofseveral packet streams and PLPs currently transmitted on a channel usingthe SLT. The transmission path information may include an IP address, aUDP port number, a session ID, a PLP ID, etc. Here, depending onembodiments, a value previously designated by the IANA or a system maybe used as an IP/UDP address. The information may be acquired using ascheme of accessing a DB or a shared memory, etc.

When the link layer signal and service data are transmitted through thesame PLP, or only one PLP is operated, service data delivered throughthe PLP may be temporarily stored in a device such as a buffer, etc.while the link layer signal is decoded.

It is possible to acquire information about a path through which theservice is actually transmitted using service signaling information of aservice to be received. In addition, a received packet stream may besubjected to decapsulation and header recovery using information such asoverhead reduction for a PLP to be received, etc.

In the illustrated example (tsib17020), the FIC and the EAC are used,and a concept of the base DP/PLP is presumed. As described in theforegoing, concepts of the FIC, the EAC, and the base DP/PLP may not beused.

While MISO or MIMO uses two antennas in the following for convenience ofdescription, the present invention is applicable to systems using two ormore antennas. The present invention proposes a physical profile (orsystem) optimized to minimize receiver complexity while attaining theperformance required for a particular use case. Physical (PHY) profiles(base, handheld and advanced profiles) according to an embodiment of thepresent invention are subsets of all configurations that a correspondingreceiver should implement. The PHY profiles share most of the functionalblocks but differ slightly in specific blocks and/or parameters. For thesystem evolution, future profiles may also be multiplexed with existingprofiles in a single radio frequency (RF) channel through a futureextension frame (FEF). The base profile and the handheld profileaccording to the embodiment of the present invention refer to profilesto which MIMO is not applied, and the advanced profile refers to aprofile to which MIMO is applied. The base profile may be used as aprofile for both the terrestrial broadcast service and the mobilebroadcast service. That is, the base profile may be used to define aconcept of a profile which includes the mobile profile. In addition, theadvanced profile may be divided into an advanced profile for a baseprofile with MIMO and an advanced profile for a handheld profile withMIMO. Moreover, the profiles may be changed according to intention ofthe designer.

The following terms and definitions may be applied to the presentinvention. The following terms and definitions may be changed accordingto design.

Auxiliary stream: sequence of cells carrying data of as yet undefinedmodulation and coding, which may be used for future extensions or asrequired by broadcasters or network operators

Base data pipe: data pipe that carries service signaling data

Baseband frame (or BBFRAME): set of Kbch bits which form the input toone FEC encoding process (BCH and LDPC encoding)

Cell: modulation value that is carried by one carrier of orthogonalfrequency division multiplexing (OFDM) transmission

Coded block: LDPC-encoded block of PLS1 data or one of the LDPC-encodedblocks of PLS2 data

Data pipe: logical channel in the physical layer that carries servicedata or related metadata, which may carry one or a plurality ofservice(s) or service component(s).

Data pipe unit (DPU): a basic unit for allocating data cells to a DP ina frame.

Data symbol: OFDM symbol in a frame which is not a preamble symbol (thedata symbol encompasses the frame signaling symbol and frame edgesymbol)

DP_ID: this 8-bit field identifies uniquely a DP within the systemidentified by the SYSTEM ID

Dummy cell: cell carrying a pseudo-random value used to fill theremaining capacity not used for PLS signaling, DPs or auxiliary streams

Emergency alert channel (EAC): part of a frame that carries EASinformation data

Frame: physical layer time slot that starts with a preamble and endswith a frame edge symbol

Frame repetition unit: a set of frames belonging to the same ordifferent physical layer profiles including an FEF, which is repeatedeight times in a superframe

Fast information channel (FIC): a logical channel in a frame thatcarries mapping information between a service and the corresponding baseDP

FECBLOCK: set of LDPC-encoded bits of DP data

FFT size: nominal FFT size used for a particular mode, equal to theactive symbol period Ts expressed in cycles of an elementary period T

Frame signaling symbol: OFDM symbol with higher pilot density used atthe start of a frame in certain combinations of FFT size, guard intervaland scattered pilot pattern, which carries a part of the PLS data

Frame edge symbol: OFDM symbol with higher pilot density used at the endof a frame in certain combinations of FFT size, guard interval andscattered pilot pattern

Frame group: the set of all frames having the same PHY profile type in asuperframe.

Future extension frame: physical layer time slot within the superframethat may be used for future extension, which starts with a preamble

Futurecast UTB system: proposed physical layer broadcast system, theinput of which is one or more MPEG2-TS, IP or general stream(s) and theoutput of which is an RF signal

Input stream: a stream of data for an ensemble of services delivered tothe end users by the system

Normal data symbol: data symbol excluding the frame signaling symbol andthe frame edge symbol

PHY profile: subset of all configurations that a corresponding receivershould implement

PLS: physical layer signaling data including PLS1 and PLS2

PLS1: a first set of PLS data carried in a frame signaling symbol (FSS)having a fixed size, coding and modulation, which carries basicinformation about a system as well as parameters needed to decode PLS2

NOTE: PLS1 data remains constant for the duration of a frame group

PLS2: a second set of PLS data transmitted in the FSS, which carriesmore detailed PLS data about the system and the DPs

PLS2 dynamic data: PLS2 data that dynamically changes frame-by-frame

PLS2 static data: PLS2 data that remains static for the duration of aframe group

Preamble signaling data: signaling data carried by the preamble symboland used to identify the basic mode of the system

Preamble symbol: fixed-length pilot symbol that carries basic PLS dataand is located at the beginning of a frame

The preamble symbol is mainly used for fast initial band scan to detectthe system signal, timing thereof, frequency offset, and FFT size.

Reserved for future use: not defined by the present document but may bedefined in future

Superframe: set of eight frame repetition units

Time interleaving block (TI block): set of cells within which timeinterleaving is carried out, corresponding to one use of a timeinterleaver memory

TI group: unit over which dynamic capacity allocation for a particularDP is carried out, made up of an integer, dynamically varying number ofXFECBLOCKs

NOTE: The TI group may be mapped directly to one frame or may be mappedto a plurality of frames. The TI group may contain one or more TIblocks.

Type 1 DP: DP of a frame where all DPs are mapped to the frame in timedivision multiplexing (TDM) scheme

Type 2 DP: DP of a frame where all DPs are mapped to the frame infrequency division multiplexing (FDM) scheme

XFECBLOCK: set of N_(cells) cells carrying all the bits of one LDPCFECBLOCK

FIG. 18 illustrates a configuration of a broadcast signal transmissionapparatus for future broadcast services according to an embodiment ofthe present invention.

The broadcast signal transmission apparatus for future broadcastservices according to the present embodiment may include an inputformatting block 1000, a bit interleaved coding & modulation (BICM)block 1010, a frame building block 1020, an OFDM generation block 1030and a signaling generation block 1040. Description will be given of anoperation of each block of the broadcast signal transmission apparatus.

In input data according to an embodiment of the present invention, IPstream/packets and MPEG2-TS may be main input formats, and other streamtypes are handled as general streams. In addition to these data inputs,management information is input to control scheduling and allocation ofthe corresponding bandwidth for each input stream. In addition, thepresent invention allows simultaneous input of one or a plurality of TSstreams, IP stream(s) and/or a general stream(s).

The input formatting block 1000 may demultiplex each input stream intoone or a plurality of data pipes, to each of which independent codingand modulation are applied. A DP is the basic unit for robustnesscontrol, which affects QoS. One or a plurality of services or servicecomponents may be carried by one DP. The DP is a logical channel in aphysical layer for delivering service data or related metadata capableof carrying one or a plurality of services or service components.

In addition, a DPU is a basic unit for allocating data cells to a DP inone frame.

An input to the physical layer may include one or a plurality of datastreams. Each of the data streams is delivered by one DP. The inputformatting block 1000 may covert a data stream input through one or morephysical paths (or DPs) into a baseband frame (BBF). In this case, theinput formatting block 1000 may perform null packet deletion or headercompression on input data (a TS or IP input stream) in order to enhancetransmission efficiency. A receiver may have a priori information for aparticular part of a header, and thus this known information may bedeleted from a transmitter. A null packet deletion block 3030 may beused only for a TS input stream.

In the BICM block 1010, parity data is added for error correction andencoded bit streams are mapped to complex-value constellation symbols.The symbols are interleaved across a specific interleaving depth that isused for the corresponding DP. For the advanced profile, MIMO encodingis performed in the BICM block 1010 and an additional data path is addedat the output for MIMO transmission.

The frame building block 1020 may map the data cells of the input DPsinto the OFDM symbols within a frame, and perform frequency interleavingfor frequency-domain diversity, especially to combat frequency-selectivefading channels. The frame building block 1020 may include a delaycompensation block, a cell mapper and a frequency interleaver.

The delay compensation block may adjust timing between DPs andcorresponding PLS data to ensure that the DPs and the corresponding PLSdata are co-timed at a transmitter side. The PLS data is delayed by thesame amount as the data pipes by addressing the delays of data pipescaused by the input formatting block and BICM block. The delay of theBICM block is mainly due to the time interleaver. In-band signaling datacarries information of the next TI group so that the information iscarried one frame ahead of the DPs to be signaled. The delaycompensation block delays in-band signaling data accordingly.

The cell mapper may map PLS, DPs, auxiliary streams, dummy cells, etc.to active carriers of the OFDM symbols in the frame. The basic functionof the cell mapper 7010 is to map data cells produced by the TIs foreach of the DPs, PLS cells, and EAC/FIC cells, if any, into arrays ofactive OFDM cells corresponding to each of the OFDM symbols within aframe. A basic function of the cell mapper is to map a data cellgenerated by time interleaving for each DP and PLS cell to an array ofactive OFDM cells (if present) corresponding to respective OFDM symbolsin one frame. Service signaling data (such as program specificinformation (PSI)/SI) may be separately gathered and sent by a DP. Thecell mapper operates according to dynamic information produced by ascheduler and the configuration of a frame structure. The frequencyinterleaver may randomly interleave data cells received from the cellmapper to provide frequency diversity. In addition, the frequencyinterleaver may operate on an OFDM symbol pair including two sequentialOFDM symbols using a different interleaving-seed order to obtain maximuminterleaving gain in a single frame.

The OFDM generation block 1030 modulates OFDM carriers by cells producedby the frame building block, inserts pilots, and produces a time domainsignal for transmission. In addition, this block subsequently insertsguard intervals, and applies peak-to-average power ratio (PAPR)reduction processing to produce a final RF signal.

Specifically, after inserting a preamble at the beginning of each frame,the OFDM generation block 1030 may apply conventional OFDM modulationhaving a cyclic prefix as a guard interval. For antenna space diversity,a distributed MISO scheme is applied across transmitters. In addition, aPAPR scheme is performed in the time domain. For flexible networkplanning, the present invention provides a set of various FFT sizes,guard interval lengths and corresponding pilot patterns.

In addition, the present invention may multiplex signals of a pluralityof broadcast transmission/reception systems in the time domain such thatdata of two or more different broadcast transmission/reception systemsproviding broadcast services may be simultaneously transmitted in thesame RF signal bandwidth. In this case, the two or more differentbroadcast transmission/reception systems refer to systems providingdifferent broadcast services. The different broadcast services may referto a terrestrial broadcast service, mobile broadcast service, etc.

The signaling generation block 1040 may create physical layer signalinginformation used for an operation of each functional block. Thissignaling information is also transmitted so that services of interestare properly recovered at a receiver side. Signaling informationaccording to an embodiment of the present invention may include PLSdata. PLS provides the receiver with a means to access physical layerDPs. The PLS data includes PLS1 data and PLS2 data.

The PLS1 data is a first set of PLS data carried in an FSS symbol in aframe having a fixed size, coding and modulation, which carries basicinformation about the system in addition to the parameters needed todecode the PLS2 data. The PLS1 data provides basic transmissionparameters including parameters required to enable reception anddecoding of the PLS2 data. In addition, the PLS1 data remains constantfor the duration of a frame group.

The PLS2 data is a second set of PLS data transmitted in an FSS symbol,which carries more detailed PLS data about the system and the DPs. ThePLS2 contains parameters that provide sufficient information for thereceiver to decode a desired DP. The PLS2 signaling further includes twotypes of parameters, PLS2 static data (PLS2-STAT data) and PLS2 dynamicdata (PLS2-DYN data). The PLS2 static data is PLS2 data that remainsstatic for the duration of a frame group and the PLS2 dynamic data isPLS2 data that dynamically changes frame by frame. Details of the PLSdata will be described later.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 19, including views (a) and (b), illustrates a BICM block accordingto an embodiment of the present invention.

The BICM block illustrated in FIG. 22 corresponds to an embodiment ofthe BICM block 1010 described with reference to FIG. 18.

As described above, the broadcast signal transmission apparatus forfuture broadcast services according to the embodiment of the presentinvention may provide a terrestrial broadcast service, mobile broadcastservice, UHDTV service, etc.

Since QoS depends on characteristics of a service provided by thebroadcast signal transmission apparatus for future broadcast servicesaccording to the embodiment of the present invention, data correspondingto respective services needs to be processed using different schemes.Accordingly, the BICM block according to the embodiment of the presentinvention may independently process respective DPs by independentlyapplying SISO, MISO and MIMO schemes to data pipes respectivelycorresponding to data paths. Consequently, the broadcast signaltransmission apparatus for future broadcast services according to theembodiment of the present invention may control QoS for each service orservice component transmitted through each DP.

FIG. 19 (a) shows a BICM block applied to a profile (or system) to whichMIMO is not applied, and FIG. 19 (b) shows a BICM block of a profile (orsystem) to which MIMO is applied.

The BICM block to which MIMO is not applied and the BICM block to whichMIMO is applied may include a plurality of processing blocks forprocessing each DP.

Description will be given of each processing block of the BICM block towhich MIMO is not applied and the BICM block to which MIMO is applied.

A processing block 5000 of the BICM block to which MIMO is not appliedmay include a data FEC encoder 5010, a bit interleaver 5020, aconstellation mapper 5030, a signal space diversity (SSD) encoding block5040 and a time interleaver 5050.

The data FEC encoder 5010 performs FEC encoding on an input BBF togenerate FECBLOCK procedure using outer coding (BCH) and inner coding(LDPC). The outer coding (BCH) is optional coding method. A detailedoperation of the data FEC encoder 5010 will be described later.

The bit interleaver 5020 may interleave outputs of the data FEC encoder5010 to achieve optimized performance with a combination of LDPC codesand a modulation scheme while providing an efficiently implementablestructure. A detailed operation of the bit interleaver 5020 will bedescribed later.

The constellation mapper 5030 may modulate each cell word from the bitinterleaver 5020 in the base and the handheld profiles, or each cellword from the cell-word demultiplexer 5010-1 in the advanced profileusing either QPSK, QAM-16, non-uniform QAM (NUQ-64, NUQ-256, orNUQ-1024) or non-uniform constellation (NUC-16, NUC-64, NUC-256, orNUC-1024) mapping to give a power-normalized constellation point, e₁.This constellation mapping is applied only for DPs. It is observed thatQAM-16 and NUQs are square shaped, while NUCs have arbitrary shapes.When each constellation is rotated by any multiple of 90 degrees, therotated constellation exactly overlaps with its original one. This“rotation-sense” symmetric property makes the capacities and the averagepowers of the real and imaginary components equal to each other. BothNUQs and NUCs are defined specifically for each code rate and theparticular one used is signaled by the parameter DP MOD filed in thePLS2 data.

The time interleaver 5050 may operates at a DP level. Parameters of timeinterleaving (TI) may be set differently for each DP. A detailedoperation of the time interleaver 5050 will be described later.

A processing block 5000-1 of the BICM block to which MIMO is applied mayinclude the data FEC encoder, the bit interleaver, the constellationmapper, and the time interleaver.

However, the processing block 5000-1 is distinguished from theprocessing block 5000 of the BICM block to which MIMO is not applied inthat the processing block 5000-1 further includes a cell-worddemultiplexer 5010-1 and a MIMO encoding block 5020-1.

In addition, operations of the data FEC encoder, the bit interleaver,the constellation mapper, and the time interleaver in the processingblock 5000-1 correspond to those of the data FEC encoder 5010, the bitinterleaver 5020, the constellation mapper 5030, and the timeinterleaver 5050 described above, and thus description thereof isomitted.

The cell-word demultiplexer 5010-1 is used for a DP of the advancedprofile to divide a single cell-word stream into dual cell-word streamsfor MIMO processing.

The MIMO encoding block 5020-1 may process an output of the cell-worddemultiplexer 5010-1 using a MIMO encoding scheme. The MIMO encodingscheme is optimized for broadcast signal transmission. MIMO technologyis a promising way to obtain a capacity increase but depends on channelcharacteristics. Especially for broadcasting, a strong LOS component ofa channel or a difference in received signal power between two antennascaused by different signal propagation characteristics makes itdifficult to obtain capacity gain from MIMO. The proposed MIMO encodingscheme overcomes this problem using rotation-based precoding and phaserandomization of one of MIMO output signals.

MIMO encoding is intended for a 2×2 MIMO system requiring at least twoantennas at both the transmitter and the receiver. A MIMO encoding modeof the present invention may be defined as full-rate spatialmultiplexing (FR-SM). FR-SM encoding may provide capacity increase withrelatively small complexity increase at the receiver side. In addition,the MIMO encoding scheme of the present invention has no restriction onan antenna polarity configuration.

MIMO processing is applied at the DP level. NUQ (e_(1,i) and e_(2,i))corresponding to a pair of constellation mapper outputs is fed to aninput of a MIMO encoder. Paired MIMO encoder output (g_(1,i) andg_(2,i)) is transmitted by the same carrier k and OFDM symbol l ofrespective TX antennas thereof.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 20 illustrates a BICM block according to another embodiment of thepresent invention.

The BICM block illustrated in FIG. 20 corresponds to another embodimentof the BICM block 1010 described with reference to FIG. 18.

FIG. 20 illustrates a BICM block for protection of physical layersignaling (PLS), an emergency alert channel (EAC) and a fast informationchannel (FIC). The EAC is a part of a frame that carries EAS informationdata, and the FIC is a logical channel in a frame that carries mappinginformation between a service and a corresponding base DP. Details ofthe EAC and FIC will be described later.

Referring to FIG. 20, the BICM block for protection of the PLS, the EACand the FIC may include a PLS FEC encoder 6000, a bit interleaver 6010and a constellation mapper 6020.

In addition, the PLS FEC encoder 6000 may include a scrambler, a BCHencoding/zero insertion block, an LDPC encoding block and an LDPC paritypuncturing block. Description will be given of each block of the BICMblock.

The PLS FEC encoder 6000 may encode scrambled PLS 1/2 data, EAC and FICsections.

The scrambler may scramble PLS1 data and PLS2 data before BCH encodingand shortened and punctured LDPC encoding.

The BCH encoding/zero insertion block may perform outer encoding on thescrambled PLS 1/2 data using a shortened BCH code for PLS protection,and insert zero bits after BCH encoding. For PLS 1 data only, outputbits of zero insertion may be permuted before LDPC encoding.

The LDPC encoding block may encode an output of the BCH encoding/zeroinsertion block using an LDPC code. To generate a complete coded block,C_(ldpc) and parity bits P_(ldpc) are encoded systematically from eachzero-inserted PLS information block I_(ldpc) and appended thereto.

C _(ldpc) =[I _(ldpc) P _(ldpc) ]=[i ₀ ,i ₁ , . . . ,i _(K) _(ldpc) ⁻¹,p ₀ ,p ₁ , . . . ,p _(N) _(ldpc) _(−K) _(ldpc) ⁻¹]  [Equation 1]

The LDPC parity puncturing block may perform puncturing on the PLS1 dataand the PLS2 data.

When shortening is applied to PLS1 data protection, some LDPC paritybits are punctured after LDPC encoding. In addition, for PLS2 dataprotection, LDPC parity bits of PLS2 are punctured after LDPC encoding.These punctured bits are not transmitted.

The bit interleaver 6010 may interleave each of shortened and puncturedPLS1 data and PLS2 data.

The constellation mapper 6020 may map the bit-interleaved PLS1 data andPLS2 data to constellations.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 21, including views (a) and (b), illustrates a bit interleavingprocess of PLS according to an embodiment of the present invention.

Each shortened and punctured PLS1 and PLS2 coded block is interleavedbit-by-bit as described in FIG. 22. Each block of additional parity bitsis interleaved with the same block interleaving structure butseparately.

In the case of BPSK, there are two branches for bit interleaving toduplicate FEC coded bits in the real and imaginary parts. Each codedblock is written to the upper branch first. The bits are mapped to thelower branch by applying modulo N c addition with cyclic shifting valuefloor(N_(FEC)/2), where N_(FEC) is the length of each LDPC coded blockafter shortening and puncturing.

In other modulation cases, such as QSPK, QAM-16 and NUQ-64, FEC codedbits are written serially into the interleaver column-wise, where thenumber of columns is the same as the modulation order.

In the read operation, the bits for one constellation symbol are readout sequentially row-wise and fed into the bit demultiplexer block.These operations are continued until the end of the column.

Each bit interleaved group is demultiplexed bit-by-bit in a group beforeconstellation mapping. Depending on modulation order, there are twomapping rules. In the case of BPSK and QPSK, the reliability of bits ina symbol is equal. Therefore, the bit group read out from the bitinterleaving block is mapped to a QAM symbol without any operation.

In the cases of QAM-16 and NUQ-64 mapped to a QAM symbol, the rule ofoperation is described in FIG. 21 (a). As shown in FIG. 21 (a), i is bitgroup index corresponding to column index in bit interleaving.

FIG. 21 (b) shows the bit demultiplexing rule for QAM-16. This operationcontinues until all bit groups are read from the bit interleaving block.

FIG. 22 illustrates a configuration of a broadcast signal receptionapparatus for future broadcast services according to an embodiment ofthe present invention.

The broadcast signal reception apparatus for future broadcast servicesaccording to the embodiment of the present invention may correspond tothe broadcast signal transmission apparatus for future broadcastservices described with reference to FIG. 18.

The broadcast signal reception apparatus for future broadcast servicesaccording to the embodiment of the present invention may include asynchronization & demodulation module 9000, a frame parsing module 9010,a demapping & decoding module 9020, an output processor 9030 and asignaling decoding module 9040. A description will be given of operationof each module of the broadcast signal reception apparatus.

The synchronization & demodulation module 9000 may receive input signalsthrough m Rx antennas, perform signal detection and synchronization withrespect to a system corresponding to the broadcast signal receptionapparatus, and carry out demodulation corresponding to a reverseprocedure of a procedure performed by the broadcast signal transmissionapparatus.

The frame parsing module 9010 may parse input signal frames and extractdata through which a service selected by a user is transmitted. If thebroadcast signal transmission apparatus performs interleaving, the frameparsing module 9010 may carry out deinterleaving corresponding to areverse procedure of interleaving. In this case, positions of a signaland data that need to be extracted may be obtained by decoding dataoutput from the signaling decoding module 9040 to restore schedulinginformation generated by the broadcast signal transmission apparatus.

The demapping & decoding module 9020 may convert input signals into bitdomain data and then deinterleave the same as necessary. The demapping &decoding module 9020 may perform demapping of mapping applied fortransmission efficiency and correct an error generated on a transmissionchannel through decoding. In this case, the demapping & decoding module9020 may obtain transmission parameters necessary for demapping anddecoding by decoding data output from the signaling decoding module9040.

The output processor 9030 may perform reverse procedures of variouscompression/signal processing procedures which are applied by thebroadcast signal transmission apparatus to improve transmissionefficiency. In this case, the output processor 9030 may acquirenecessary control information from data output from the signalingdecoding module 9040. An output of the output processor 9030 correspondsto a signal input to the broadcast signal transmission apparatus and maybe MPEG-TSs, IP streams (v4 or v6) and generic streams.

The signaling decoding module 9040 may obtain PLS information from asignal demodulated by the synchronization & demodulation module 9000. Asdescribed above, the frame parsing module 9010, the demapping & decodingmodule 9020 and the output processor 9030 may execute functions thereofusing data output from the signaling decoding module 9040.

A frame according to an embodiment of the present invention is furtherdivided into a number of OFDM symbols and a preamble. As shown in (d),the frame includes a preamble, one or more frame signaling symbols(FSSs), normal data symbols and a frame edge symbol (FES).

The preamble is a special symbol that enables fast futurecast UTB systemsignal detection and provides a set of basic transmission parameters forefficient transmission and reception of a signal. Details of thepreamble will be described later.

A main purpose of the FSS is to carry PLS data. For fast synchronizationand channel estimation, and hence fast decoding of PLS data, the FSS hasa dense pilot pattern than a normal data symbol. The FES has exactly thesame pilots as the FSS, which enables frequency-only interpolationwithin the FES and temporal interpolation, without extrapolation, forsymbols immediately preceding the FES.

FIG. 23 illustrates a signaling hierarchy structure of a frame accordingto an embodiment of the present invention.

FIG. 23 illustrates the signaling hierarchy structure, which is splitinto three main parts corresponding to preamble signaling data 11000,PLS1 data 11010 and PLS2 data 11020. A purpose of a preamble, which iscarried by a preamble symbol in every frame, is to indicate atransmission type and basic transmission parameters of the frame. PLS1enables the receiver to access and decode the PLS2 data, which containsthe parameters to access a DP of interest. PLS2 is carried in everyframe and split into two main parts corresponding to PLS2-STAT data andPLS2-DYN data. Static and dynamic portions of PLS2 data are followed bypadding, if necessary.

Preamble signaling data according to an embodiment of the presentinvention carries 21 bits of information that are needed to enable thereceiver to access PLS data and trace DPs within the frame structure.Details of the preamble signaling data are as follows.

FFT_SIZE: This 2-bit field indicates an FFT size of a current framewithin a frame group as described in the following Table 1.

TABLE 1 Value FFT size 00  8K FFT 01 16K FFT 10 32K FFT 11 Reserved

GI_FRACTION: This 3-bit field indicates a guard interval fraction valuein a current superframe as described in the following Table 2.

TABLE 2 Value GI_FRACTION 000 ⅕ 001 1/10 010 1/20 011 1/40 100 1/80 1011/160 110 to 111 Reserved

EAC_FLAG: This 1-bit field indicates whether the EAC is provided in acurrent frame. If this field is set to ‘1’, an emergency alert service(EAS) is provided in the current frame. If this field set to ‘0’, theEAS is not carried in the current frame. This field may be switcheddynamically within a superframe.

PILOT_MODE: This 1-bit field indicates whether a pilot mode is a mobilemode or a fixed mode for a current frame in a current frame group. Ifthis field is set to ‘0’, the mobile pilot mode is used. If the field isset to ‘1’, the fixed pilot mode is used.

PAPR_FLAG: This 1-bit field indicates whether PAPR reduction is used fora current frame in a current frame group. If this field is set to avalue of ‘1’, tone reservation is used for PAPR reduction. If this fieldis set to a value of ‘0’, PAPR reduction is not used.

RESERVED: This 7-bit field is reserved for future use.

FIG. 24 illustrates PLS1 data according to an embodiment of the presentinvention.

PLS1 data provides basic transmission parameters including parametersrequired to enable reception and decoding of PLS2. As mentioned above,the PLS1 data remain unchanged for the entire duration of one framegroup. A detailed definition of the signaling fields of the PLS1 data isas follows.

PREAMBLE_DATA: This 20-bit field is a copy of preamble signaling dataexcluding EAC_FLAG

NUM_FRAME_FRU: This 2-bit field indicates the number of the frames perFRU.

PAYLOAD_TYPE: This 3-bit field indicates a format of payload datacarried in a frame group. PAYLOAD_TYPE is signaled as shown in Table 3.

TABLE 3 Value Payload type 1XX TS is transmitted. X1X IP stream istransmitted. XX1 GS is transmitted.

NUM_FSS: This 2-bit field indicates the number of FSSs in a currentframe.

SYSTEM_VERSION: This 8-bit field indicates a version of a transmittedsignal format. SYSTEM_VERSION is divided into two 4-bit fields: a majorversion and a minor version.

Major version: The MSB corresponding to four bits of the SYSTEM_VERSIONfield indicate major version information. A change in the major versionfield indicates a non-backward-compatible change. A default value is‘0000’. For a version described in this standard, a value is set to‘0000’.

Minor version: The LSB corresponding to four bits of SYSTEM_VERSIONfield indicate minor version information. A change in the minor versionfield is backwards compatible.

CELL_ID: This is a 16-bit field which uniquely identifies a geographiccell in an ATSC network. An ATSC cell coverage area may include one ormore frequencies depending on the number of frequencies used perfuturecast UTB system. If a value of CELL_ID is not known orunspecified, this field is set to ‘0’.

NETWORK_ID: This is a 16-bit field which uniquely identifies a currentATSC network.

SYSTEM_ID: This 16-bit field uniquely identifies the futurecast UTBsystem within the ATSC network. The futurecast UTB system is aterrestrial broadcast system whose input is one or more input streams(TS, IP, GS) and whose output is an RF signal. The futurecast UTB systemcarries one or more PHY profiles and FEF, if any. The same futurecastUTB system may carry different input streams and use different RFs indifferent geographical areas, allowing local service insertion. Theframe structure and scheduling are controlled in one place and areidentical for all transmissions within the futurecast UTB system. One ormore futurecast UTB systems may have the same SYSTEM_ID meaning thatthey all have the same physical layer structure and configuration.

The following loop includes FRU_PHY_PROFILE, FRU_FRAME_LENGTH,FRU_GI_FRACTION, and RESERVED which are used to indicate an FRUconfiguration and a length of each frame type. A loop size is fixed sothat four PHY profiles (including an FEF) are signaled within the FRU.If NUM_FRAME_FRU is less than 4, unused fields are filled with zeros.

FRU_PHY_PROFILE: This 3-bit field indicates a PHY profile type of an(i+1)^(th) (i is a loop index) frame of an associated FRU. This fielduses the same signaling format as shown in Table 8.

FRU_FRAME_LENGTH: This 2-bit field indicates a length of an (i+1)^(th)frame of an associated FRU. Using FRU_FRAME_LENGTH together withFRU_GI_FRACTION, an exact value of a frame duration may be obtained.

FRU_GI_FRACTION: This 3-bit field indicates a guard interval fractionvalue of an (i+1)^(th) frame of an associated FRU. FRU_GI_FRACTION issignaled according to Table 7.

RESERVED: This 4-bit field is reserved for future use.

The following fields provide parameters for decoding the PLS2 data.

PLS2_FEC_TYPE: This 2-bit field indicates an FEC type used by PLS2protection. The FEC type is signaled according to Table 4. Details ofLDPC codes will be described later.

TABLE 4 Content PLS2 FEC type 00 4K-1/4 and 7K-3/10 LDPC codes 01 to 11Reserved

PLS2_MOD: This 3-bit field indicates a modulation type used by PLS2. Themodulation type is signaled according to Table 5.

TABLE 5 Value PLS2_MODE 000 BPSK 001 QPSK 010 QAM-16 011 NUQ-64 100 to111 Reserved

PLS2_SIZE_CELL: This 15-bit field indicates C_(total) _(_) _(partial)_(_) _(block), a size (specified as the number of QAM cells) of thecollection of full coded blocks for PLS2 that is carried in a currentframe group. This value is constant during the entire duration of thecurrent frame group.

PLS2_STAT_SIZE_BIT: This 14-bit field indicates a size, in bits, ofPLS2-STAT for a current frame group. This value is constant during theentire duration of the current frame group.

PLS2_DYN_SIZE_BIT: This 14-bit field indicates a size, in bits, ofPLS2-DYN for a current frame group. This value is constant during theentire duration of the current frame group.

PLS2_REP_FLAG: This 1-bit flag indicates whether a PLS2 repetition modeis used in a current frame group. When this field is set to a value of‘1’, the PLS2 repetition mode is activated. When this field is set to avalue of ‘0’, the PLS2 repetition mode is deactivated.

PLS2_REP_SIZE_CELL: This 15-bit field indicates C_(total) _(_)_(partial) _(_) _(block), a size (specified as the number of QAM cells)of the collection of partial coded blocks for PLS2 carried in everyframe of a current frame group, when PLS2 repetition is used. Ifrepetition is not used, a value of this field is equal to 0. This valueis constant during the entire duration of the current frame group.

PLS2_NEXT_FEC_TYPE: This 2-bit field indicates an FEC type used for PLS2that is carried in every frame of a next frame group. The FEC type issignaled according to Table 10.

PLS2_NEXT_MOD: This 3-bit field indicates a modulation type used forPLS2 that is carried in every frame of a next frame group. Themodulation type is signaled according to Table 11.

PLS2_NEXT_REP_FLAG: This 1-bit flag indicates whether the PLS2repetition mode is used in a next frame group. When this field is set toa value of ‘1’, the PLS2 repetition mode is activated. When this fieldis set to a value of ‘0’, the PLS2 repetition mode is deactivated.

PLS2_NEXT_REP_SIZE_CELL: This 15-bit field indicates C_(total) _(_)_(full) _(_) _(block), a size (specified as the number of QAM cells) ofthe collection of full coded blocks for PLS2 that is carried in everyframe of a next frame group, when PLS2 repetition is used. If repetitionis not used in the next frame group, a value of this field is equal to0. This value is constant during the entire duration of a current framegroup.

PLS2_NEXT_REP_STAT_SIZE_BIT: This 14-bit field indicates a size, inbits, of PLS2-STAT for a next frame group. This value is constant in acurrent frame group.

PLS2_NEXT_REP_DYN_SIZE_BIT: This 14-bit field indicates the size, inbits, of the PLS2-DYN for a next frame group. This value is constant ina current frame group.

PLS2_AP_MODE: This 2-bit field indicates whether additional parity isprovided for PLS2 in a current frame group. This value is constantduring the entire duration of the current frame group. Table 6 belowprovides values of this field. When this field is set to a value of‘00’, additional parity is not used for the PLS2 in the current framegroup.

TABLE 6 Value PLS2-AP mode 00 AP is not provided 01 AP1 mode 10 to 11Reserved

PLS2_AP_SIZE_CELL: This 15-bit field indicates a size (specified as thenumber of QAM cells) of additional parity bits of PLS2. This value isconstant during the entire duration of a current frame group.

PLS2_NEXT_AP_MODE: This 2-bit field indicates whether additional parityis provided for PLS2 signaling in every frame of a next frame group.This value is constant during the entire duration of a current framegroup. Table 12 defines values of this field

PLS2_NEXT_AP_SIZE_CELL: This 15-bit field indicates a size (specified asthe number of QAM cells) of additional parity bits of PLS2 in everyframe of a next frame group. This value is constant during the entireduration of a current frame group.

RESERVED: This 32-bit field is reserved for future use.

CRC_32: A 32-bit error detection code, which is applied to all PLS1signaling.

FIG. 25 illustrates PLS2 data according to an embodiment of the presentinvention.

FIG. 25 illustrates PLS2-STAT data of the PLS2 data. The PLS2-STAT datais the same within a frame group, while PLS2-DYN data providesinformation that is specific for a current frame.

Details of fields of the PLS2-STAT data are described below.

FIC_FLAG: This 1-bit field indicates whether the FIC is used in acurrent frame group. If this field is set to ‘1’, the FIC is provided inthe current frame. If this field set to ‘0’, the FIC is not carried inthe current frame. This value is constant during the entire duration ofa current frame group.

AUX_FLAG: This 1-bit field indicates whether an auxiliary stream is usedin a current frame group. If this field is set to ‘1’, the auxiliarystream is provided in a current frame. If this field set to ‘0’, theauxiliary stream is not carried in the current frame. This value isconstant during the entire duration of current frame group.

NUM_DP: This 6-bit field indicates the number of DPs carried within acurrent frame. A value of this field ranges from 1 to 64, and the numberof DPs is NUM_DP+1.

DP_ID: This 6-bit field identifies uniquely a DP within a PHY profile.

DP_TYPE: This 3-bit field indicates a type of a DP. This is signaledaccording to the following Table 7.

TABLE 7 Value DP Type 000 DP Type 1 001 DP Type 2 010 to 111 Reserved

DP_GROUP_ID: This 8-bit field identifies a DP group with which a currentDP is associated. This may be used by the receiver to access DPs ofservice components associated with a particular service having the sameDP_GROUP_ID.

BASE_DP_ID: This 6-bit field indicates a DP carrying service signalingdata (such as PSI/SI) used in a management layer. The DP indicated byBASE_DP_ID may be either a normal DP carrying the service signaling dataalong with service data or a dedicated DP carrying only the servicesignaling data.

DP_FEC_TYPE: This 2-bit field indicates an FEC type used by anassociated DP. The FEC type is signaled according to the following Table8.

TABLE 8 Value FEC_TYPE 00 16K LDPC 01 64K LDPC 10 to 11 Reserved

DP_COD: This 4-bit field indicates a code rate used by an associated DP.The code rate is signaled according to the following Table 9.

TABLE 9 Value Code rate 0000  5/15 0001  6/15 0010  7/15 0011  8/15 0100 9/15 0101 10/15 0110 11/15 0111 12/15 1000 13/15 1001 to 1111 Reserved

DP_MOD: This 4-bit field indicates modulation used by an associated DP.The modulation is signaled according to the following Table 10.

TABLE 10 Value Modulation 0000 QPSK 0001 QAM-16 0010 NUQ-64 0011 NUQ-2560100 NUQ-1024 0101 NUC-16 0110 NUC-64 0111 NUC-256 1000 NUC-1024 1001 to1111 Reserved

DP_SSD_FLAG: This 1-bit field indicates whether an SSD mode is used inan associated DP. If this field is set to a value of ‘1’, SSD is used.If this field is set to a value of ‘0’, SSD is not used.

The following field appears only if PHY_PROFILE is equal to ‘010’, whichindicates the advanced profile:

DP_MIMO: This 3-bit field indicates which type of MIMO encoding processis applied to an associated DP. A type of MIMO encoding process issignaled according to the following Table 11.

TABLE 11 Value MIMO encoding 000 FR-SM 001 FRFD-SM 010 to 111 Reserved

DP_TI_TYPE: This 1-bit field indicates a type of time interleaving. Avalue of ‘0’ indicates that one TI group corresponds to one frame andcontains one or more TI blocks. A value of ‘1’ indicates that one TIgroup is carried in more than one frame and contains only one TI block.

DP_TI_LENGTH: The use of this 2-bit field (allowed values are only 1, 2,4, and 8) is determined by values set within the DP_TI_TYPE field asfollows.

If DP_TI_TYPE is set to a value of ‘1’, this field indicates P_(I), thenumber of frames to which each TI group is mapped, and one TI block ispresent per TI group (N_(TI)=1). Allowed values of P_(I) with the 2-bitfield are defined in Table 12 below.

If DP_TI_TYPE is set to a value of ‘0’, this field indicates the numberof TI blocks N_(TI) per TI group, and one TI group is present per frame(P_(I)=1). Allowed values of P_(I) with the 2-bit field are defined inthe following Table 12.

TABLE 12 2-bit field P_(I) N_(TI) 00 1 1 01 2 2 10 4 3 11 8 4

DP_FRAME_INTERVAL: This 2-bit field indicates a frame interval(I_(JUMP)) within a frame group for an associated DP and allowed valuesare 1, 2, 4, and 8 (the corresponding 2-bit field is ‘00’, ‘01’, ‘10’,or ‘11’, respectively). For DPs that do not appear every frame of theframe group, a value of this field is equal to an interval betweensuccessive frames. For example, if a DP appears on frames 1, 5, 9, 13,etc., this field is set to a value of ‘4’. For DPs that appear in everyframe, this field is set to a value of ‘1’.

DP_TI_BYPASS: This 1-bit field determines availability of the timeinterleaver 5050. If time interleaving is not used for a DP, a value ofthis field is set to ‘1’. If time interleaving is used, the value is setto ‘0’.

DP_FIRST_FRAME_IDX: This 5-bit field indicates an index of a first frameof a superframe in which a current DP occurs. A value ofDP_FIRST_FRAME_IDX ranges from 0 to 31

DP_NUM_BLOCK_MAX: This 10-bit field indicates a maximum value ofDP_NUM_BLOCKS for this DP. A value of this field has the same range asDP_NUM_BLOCKS.

DP_PAYLOAD_TYPE: This 2-bit field indicates a type of payload datacarried by a given DP. DP_PAYLOAD_TYPE is signaled according to thefollowing Table 13.

TABLE 13 Value Payload Type 00 TS 01 IP 10 GS 11 Reserved

DP_INBAND_MODE: This 2-bit field indicates whether a current DP carriesin-band signaling information. An in-band signaling type is signaledaccording to the following Table 14.

TABLE 14 Value In-band mode 00 In-band signaling is not carried. 01INBAND-PLS is carried 10 INBAND-ISSY is carried 11 INBAND-PLS andINBAND-ISSY are carried

DP_PROTOCOL_TYPE: This 2-bit field indicates a protocol type of apayload carried by a given DP. The protocol type is signaled accordingto Table 15 below when input payload types are selected.

TABLE 15 If DP_PAY- If DP_PAY- If DP_PAY- LOAD_TYPE LOAD_TYPE LOAD_TYPEValue is TS is IP is GS 00 MPEG2-TS IPv4 (Note) 01 Reserved IPv6Reserved 10 Reserved Reserved Reserved 11 Reserved Reserved Reserved

DP_CRC_MODE: This 2-bit field indicates whether CRC encoding is used inan input formatting block. A CRC mode is signaled according to thefollowing Table 16.

TABLE 16 Value CRC mode 00 Not used 01 CRC-8 10 CRC-16 11 CRC-32

DNP_MODE: This 2-bit field indicates a null-packet deletion mode used byan associated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). DNP_MODE issignaled according to Table 17 below. If DP_PAYLOAD_TYPE is not TS(‘00’), DNP_MODE is set to a value of ‘00’.

TABLE 17 Value Null-packet deletion mode 00 Not used 01 DNP-NORMAL 10DNP-OFFSET 11 Reserved

ISSY_MODE: This 2-bit field indicates an ISSY mode used by an associatedDP when DP_PAYLOAD_TYPE is set to TS (‘00’). ISSY_MODE is signaledaccording to Table 18 below. If DP_PAYLOAD_TYPE is not TS (‘00’),ISSY_MODE is set to the value of ‘00’.

TABLE 18 Value ISSY mode 00 Not used 01 ISSY-UP 10 ISSY-BBF 11 Reserved

HC_MODE_TS: This 2-bit field indicates a TS header compression mode usedby an associated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). HC_MODE_TSis signaled according to the following Table 19.

TABLE 19 Value Header compression mode 00 HC_MODE_TS 1 01 HC_MODE_TS 210 HC_MODE_TS 3 11 HC_MODE_TS 4

HC_MODE_IP: This 2-bit field indicates an IP header compression modewhen DP_PAYLOAD_TYPE is set to IP (‘01’). HC_MODE_IP is signaledaccording to the following Table 20.

TABLE 20 Value Header compression mode 00 No compression 01 HC_MODE_IP 110 to 11 Reserved

PID: This 13-bit field indicates the PID number for TS headercompression when DP_PAYLOAD_TYPE is set to TS (‘00’) and HC_MODE_TS isset to ‘01’ or ‘10’.

RESERVED: This 8-bit field is reserved for future use.

The following fields appear only if FIC_FLAG is equal to ‘1’.

FIC_VERSION: This 8-bit field indicates the version number of the FIC.

FIC_LENGTH_BYTE: This 13-bit field indicates the length, in bytes, ofthe FIC.

RESERVED: This 8-bit field is reserved for future use.

The following fields appear only if AUX_FLAG is equal to ‘1’.

NUM_AUX: This 4-bit field indicates the number of auxiliary streams.Zero means no auxiliary stream is used.

AUX_CONFIG_RFU: This 8-bit field is reserved for future use.

AUX_STREAM_TYPE: This 4-bit is reserved for future use for indicating atype of a current auxiliary stream.

AUX_PRIVATE_CONFIG: This 28-bit field is reserved for future use forsignaling auxiliary streams.

FIG. 26 illustrates PLS2 data according to another embodiment of thepresent invention.

FIG. 26 illustrates PLS2-DYN data of the PLS2 data. Values of thePLS2-DYN data may change during the duration of one frame group whilesizes of fields remain constant.

Details of fields of the PLS2-DYN data are as below.

FRAME_INDEX: This 5-bit field indicates a frame index of a current framewithin a superframe. An index of a first frame of the superframe is setto ‘0’.

PLS_CHANGE_COUNTER: This 4-bit field indicates the number of superframesbefore a configuration changes. A next superframe with changes in theconfiguration is indicated by a value signaled within this field. Ifthis field is set to a value of ‘0000’, it means that no scheduledchange is foreseen. For example, a value of ‘1’ indicates that there isa change in the next superframe.

FIC_CHANGE_COUNTER: This 4-bit field indicates the number of superframesbefore a configuration (i.e., content of the FIC) changes. A nextsuperframe with changes in the configuration is indicated by a valuesignaled within this field. If this field is set to a value of ‘0000’,it means that no scheduled change is foreseen. For example, a value of‘0001’ indicates that there is a change in the next superframe.

RESERVED: This 16-bit field is reserved for future use.

The following fields appear in a loop over NUM_DP, which describeparameters associated with a DP carried in a current frame.

DP_ID: This 6-bit field uniquely indicates a DP within a PHY profile.

DP_START: This 15-bit (or 13-bit) field indicates a start position ofthe first of the DPs using a DPU addressing scheme. The DP_START fieldhas differing length according to the PHY profile and FFT size as shownin the following Table 21.

TABLE 21 DP_START field size PHY profile 64K 16K Base 13 bits 15 bitsHandheld — 13 bits Advanced 13 bits 15 bits

DP_NUM_BLOCK: This 10-bit field indicates the number of FEC blocks in acurrent TI group for a current DP. A value of DP_NUM_BLOCK ranges from 0to 1023.

RESERVED: This 8-bit field is reserved for future use.

The following fields indicate FIC parameters associated with the EAC.

EAC_FLAG: This 1-bit field indicates the presence of the EAC in acurrent frame. This bit is the same value as EAC_FLAG in a preamble.

EAS_WAKE_UP_VERSION NUM: This 8-bit field indicates a version number ofa wake-up indication.

If the EAC_FLAG field is equal to ‘1’, the following 12 bits areallocated to EAC LENGTH BYTE.

If the EAC_FLAG field is equal to ‘0’, the following 12 bits areallocated to EAC COUNTER.

EAC_LENGTH_BYTE: This 12-bit field indicates a length, in bytes, of theEAC.

EAC_COUNTER: This 12-bit field indicates the number of frames before aframe where the EAC arrives.

The following fields appear only if the AUX_FLAG field is equal to ‘1’.

AUX_PRIVATE_DYN: This 48-bit field is reserved for future use forsignaling auxiliary streams. A meaning of this field depends on a valueof AUX_STREAM_TYPE in a configurable PLS2-STAT.

CRC_32: A 32-bit error detection code, which is applied to the entirePLS2.

FIG. 27 illustrates a logical structure of a frame according to anembodiment of the present invention.

As above mentioned, the PLS, EAC, FIC, DPs, auxiliary streams and dummycells are mapped to the active carriers of OFDM symbols in a frame. PLS1and PLS2 are first mapped to one or more FSSs. Thereafter, EAC cells, ifany, are mapped to an immediately following PLS field, followed next byFIC cells, if any. The DPs are mapped next after the PLS or after theEAC or the FIC, if any. Type 1 DPs are mapped first and Type 2 DPs aremapped next. Details of types of the DPs will be described later. Insome cases, DPs may carry some special data for EAS or service signalingdata. The auxiliary streams or streams, if any, follow the DPs, which inturn are followed by dummy cells. When the PLS, EAC, FIC, DPs, auxiliarystreams and dummy data cells are mapped all together in the abovementioned order, i.e. the PLS, EAC, FIC, DPs, auxiliary streams anddummy data cells, cell capacity in the frame is exactly filled.

FIG. 28 illustrates PLS mapping according to an embodiment of thepresent invention.

PLS cells are mapped to active carriers of FSS(s). Depending on thenumber of cells occupied by PLS, one or more symbols are designated asFSS(s), and the number of FSS(s) NFSS is signaled by NUM_FSS in PLS1.The FSS is a special symbol for carrying PLS cells. Since robustness andlatency are critical issues in the PLS, the FSS(s) have higher pilotdensity, allowing fast synchronization and frequency-only interpolationwithin the FSS.

PLS cells are mapped to active carriers of the FSS(s) in a top-downmanner as shown in the figure. PLS1 cells are mapped first from a firstcell of a first FSS in increasing order of cell index. PLS2 cells followimmediately after a last cell of PLS1 and mapping continues downwarduntil a last cell index of the first FSS. If the total number ofrequired PLS cells exceeds the number of active carriers of one FSS,mapping proceeds to a next FSS and continues in exactly the same manneras the first FSS.

After PLS mapping is completed, DPs are carried next. If an EAC, an FICor both are present in a current frame, the EAC and the FIC are placedbetween the PLS and “normal” DPs.

Hereinafter, description will be given of encoding an FEC structureaccording to an embodiment of the present invention. As above mentioned,the data FEC encoder may perform FEC encoding on an input BBF togenerate an FECBLOCK procedure using outer coding (BCH), and innercoding (LDPC). The illustrated FEC structure corresponds to theFECBLOCK. In addition, the FECBLOCK and the FEC structure have samevalue corresponding to a length of an LDPC codeword.

As described above, BCH encoding is applied to each BBF (K_(bch) bits),and then LDPC encoding is applied to BCH-encoded BBF (K_(ldpc)bits=N_(bch) bits).

A value of N_(ldpc) is either 64,800 bits (long FECBLOCK) or 16,200 bits(short FECBLOCK).

Table 22 and Table 23 below show FEC encoding parameters for the longFECBLOCK and the short FECBLOCK, respectively.

TABLE 22 BCH error correction LDPC rate N_(ldpc) K_(ldpc) K_(bch)capability N_(bch) − K_(bch) 5/15 64800 21600 21408 12 192 6/15 2592025728 7/15 30240 30048 8/15 34560 34368 9/15 38880 38688 10/15  4320043008 11/15  47520 47328 12/15  51840 51648 13/15  56160 55968

TABLE 23 BCH error correction LDPC rate N_(ldpc) K_(ldpc) K_(bch)capability N_(bch) − K_(bch) 5/15 16200 5400 5232 12 168 6/15 6480 63127/15 7560 7392 8/15 8640 8472 9/15 9720 9552 10/15  10800 10632 11/15 11880 11712 12/15  12960 12792 13/15  14040 13872

Detailed operations of BCH encoding and LDPC encoding are as below.

A 12-error correcting BCH code is used for outer encoding of the BBF. ABCH generator polynomial for the short FECBLOCK and the long FECBLOCKare obtained by multiplying all polynomials together.

LDPC code is used to encode an output of outer BCH encoding. To generatea completed B_(ldpc) (FECBLOCK), P_(ldpc) (parity bits) is encodedsystematically from each I_(ldpc)(BCH—encoded BBF), and appended toI_(ldpc). The completed B_(ldpc) (FECBLOCK) is expressed by thefollowing Equation.

B _(ldpc) =[I _(ldpc) P _(ldpc) ]=[i ₀ ,i ₁ , . . . ,i _(K) _(ldpc) ⁻¹,p ₀ ,p ₁ , . . . ,p _(N) _(ldpc) _(−K) _(ldpc) ⁻¹]  [Equation 2]

Parameters for the long FECBLOCK and the short FECBLOCK are given in theabove Tables 22 and 23, respectively.

A detailed procedure to calculate N_(ldpc)−K_(ldpc) parity bits for thelong FECBLOCK, is as follows.

1) Initialize the parity bits

p ₀ =p ₁ p ₂ = . . . =p _(N) _(ldpc) _(−K) _(ldpc) ⁻¹=0  [Equation 3]

2) Accumulate a first information bit—i₀, at a parity bit addressspecified in a first row of addresses of a parity check matrix. Detailsof the addresses of the parity check matrix will be described later. Forexample, for the rate of 13/15,

p ₉₈₃ =p ₉₈₃ ⊕i ₀ p ₂₈₁₅ =p ₂₈₁₅ ⊕i ₀

p ₄₈₃₇ =p ₄₈₃₇ ⊕i ₀ p ₄₉₈₉ =p ₄₉₈₉ ⊕i ₀

p ₆₁₃₈ =p ₆₁₃₈ ⊕i ₀ p ₆₄₅₈ =p ₆₄₅₈ ⊕i ₀

p ₆₉₂₁ =p ₆₉₂₁ ⊕i ₀ p ₆₉₇₄ =p ₆₉₇₄ ⊕i ₀

p ₇₅₇₂ =p ₇₅₇₂ ⊕i ₀ p ₈₂₆₀ =p ₈₂₆₀ ⊕i ₀

p ₈₄₉₆=₈₄₉₆ ⊕i ₀  [Equation 4]

3) For the next 359 information bits, i_(s), s=1, 2, . . . , 359,accumulate is at parity bit addresses using following Equation.

{x+(s mod 360)×Q _(ldpc)} mod(N _(ldpc) −K _(ldpc))  [Equation 5]

Here, x denotes an address of a parity bit accumulator corresponding toa first bit i₀, and Q_(ldpc) is a code rate dependent constant specifiedin the addresses of the parity check matrix. Continuing with theexample, Q_(ldpc)=24 for the rate of 13/15, so for an information biti₁, the following operations are performed.

p ₁₀₀₇ =p ₁₀₀₇ ⊕i ₁ p ₂₈₃₉ =p ₂₈₃₉ ⊕i ₁

p ₄₈₆₁ =p ₄₈₆₁ ⊕i ₁ p ₅₀₁₃ =p ₅₀₁₃ ⊕i ₁

p ₆₁₆₂ =p ₆₁₆₂ ⊕i ₁ p ₆₄₈₂ =p ₆₄₈₂ ⊕i ₁

p ₆₉₄₅ =p ₆₉₄₅ ⊕i ₁ p ₆₉₉₈ =p ₆₉₉₈ ⊕i ₁

p ₇₅₉₆ =p ₇₅₉₆ ⊕i ₁ p ₈₂₈₄ =p ₈₂₈₄ ⊕i ₁

p ₈₅₂₀ =p ₈₅₂₀ ⊕i ₁  [Equation 6]

4) For a 361th information bit i₃₆₀, an address of the parity bitaccumulator is given in a second row of the addresses of the paritycheck matrix. In a similar manner, addresses of the parity bitaccumulator for the following 359 information bits i_(s), s=361, 362, .. . , 719 are obtained using Equation 6, where x denotes an address ofthe parity bit accumulator corresponding to the information bit i₃₆₀,i.e., an entry in the second row of the addresses of the parity checkmatrix.

5) In a similar manner, for every group of 360 new information bits, anew row from the addresses of the parity check matrix is used to findthe address of the parity bit accumulator.

After all of the information bits are exhausted, a final parity bit isobtained as below.

6) Sequentially perform the following operations starting with i=1.

p _(i) =p _(i) ⊕p _(i−1) ,i=1,2, . . . ,N _(ldpc) −K_(ldpc)−1  [Equation 7]

Here, final content of p_(i) (i=0, 1, . . . , N_(ldpc)−K_(ldpc)−1) isequal to a parity bit p_(i).

TABLE 24 Code rate Q_(ldpc) 5/15 120 6/15 108 7/15 96 8/15 84 9/15 7210/15  60 11/15  48 12/15  36 13/15  24

This LDPC encoding procedure for the short FECBLOCK is in accordancewith t LDPC encoding procedure for the long FECBLOCK, except that Table24 is replaced with Table 25, and the addresses of the parity checkmatrix for the long FECBLOCK are replaced with the addresses of theparity check matrix for the short FECBLOCK.

TABLE 25 Code rate Q_(ldpc) 5/15 30 6/15 27 7/15 24 8/15 21 9/15 1810/15  15 11/15  12 12/15  9 13/15  6

FIG. 29, including views (a)-(c), illustrates time interleavingaccording to an embodiment of the present invention.

FIG. 29 shows examples of a time interleaving (TI) mode.

A time interleaver operates at the DP level. Parameters of TI may be setdifferently for each DP.

The following parameters, which appear in part of the PLS2-STAT data,configure the TI.

DP_TI TYPE (allowed values: 0 or 1): This parameter represents the TImode. The value of ‘0’ indicates a mode with multiple TI blocks (morethan one TI block) per TI group. In this case, one TI group is directlymapped to one frame (no inter-frame interleaving). The value of ‘1’indicates a mode with only one TI block per TI group. In this case, theTI block may be spread over more than one frame (inter-frameinterleaving).

DP_TI_LENGTH: If DP_TI_TYPE=‘0’, this parameter is the number of TIblocks N_(TI) per TI group. For DP_TI_TYPE=‘1’, this parameter is thenumber of frames P_(I) spread from one TI group.

DP_NUM_BLOCK_MAX (allowed values: 0 to 1023): This parameter representsthe maximum number of XFECBLOCKs per TI group.

DP_FRAME_INTERVAL (allowed values: 1, 2, 4, and 8): This parameterrepresents the number of the frames I_(JUMP) between two successiveframes carrying the same DP of a given PHY profile.

DP_TI_BYPASS (allowed values: 0 or 1): If time interleaving is not usedfor a DP, this parameter is set to ‘1’. This parameter is set to ‘0’ iftime interleaving is used.

Additionally, the parameter DP_NUM_BLOCK from the PLS2-DYN data is usedto represent the number of XFECBLOCKs carried by one TI group of the DP.

When time interleaving is not used for a DP, the following TI group,time interleaving operation, and TI mode are not considered. However,the delay compensation block for the dynamic configuration informationfrom the scheduler may still be required. In each DP, the XFECBLOCKsreceived from SSD/MIMO encoding are grouped into TI groups. That is,each TI group is a set of an integer number of XFECBLOCKs and contains adynamically variable number of XFECBLOCKs. The number of XFECBLOCKs inthe TI group of index n is denoted by N_(xBLOCK) _(_) _(Group)(n) and issignaled as DP_NUM_BLOCK in the PLS2-DYN data. Note that N_(xBLOCK) _(_)_(Group)(n) may vary from a minimum value of 0 to a maximum value ofN_(xBLOCK) _(_) _(Group) _(_) _(MAX) (corresponding toDP_NUM_BLOCK_MAX), the largest value of which is 1023.

Each TI group is either mapped directly to one frame or spread overP_(I) frames. Each TI group is also divided into more than one TI block(N_(TI)), where each TI block corresponds to one usage of a timeinterleaver memory. The TI blocks within the TI group may containslightly different numbers of XFECBLOCKs. If the TI group is dividedinto multiple TI blocks, the TI group is directly mapped to only oneframe. There are three options for time interleaving (except an extraoption of skipping time interleaving) as shown in the following Table26.

TABLE 26 Modes Descriptions Option 1 Each TI group contains one TI blockand is mapped directly to one frame as shown in (a). This option issignaled in PLS2-STAT by DP_TI_TYPE = ‘0’ and DP_TI_LENGTH = ‘1’ (N_(TI)= 1). Option 2 Each TI group contains one TI block and is mapped to morethan one frame. (b) shows an example, where one TI group is mapped totwo frames, i.e., DP_TI_LENGTH = ‘2’ (P_(I) = 2) and DP_FRAME_INTERVAL(I_(JUMP) = 2). This provides greater time diversity for low data-rateservices. This option is signaled in the PLS2-STAT by DP_TI_TYPE = ‘1’.Option 3 Each TI group is divided into multiple TI blocks and is mappeddirectly to one frame as shown in (c). Each TI block may use a full TImemory so as to provide the maximum bit- rate for a DP. This option issignaled in the PLS2-STAT by DP_TI_TYPE = ‘0’ and DP_TI_LENGTH = N_(TI),while P_(I) = 1.

Typically, the time interleaver may also function as a buffer for DPdata prior to a process of frame building. This is achieved by means oftwo memory banks for each DP. A first TI block is written to a firstbank. A second TI block is written to a second bank while the first bankis being read from and so on.

The TI is a twisted row-column block interleaver. For an s^(th) TI blockof an n^(th) TI group, the number of rows N_(r) of a TI memory is equalto the number of cells N_(cells), i.e., N_(r)=N_(cells) while the numberof columns N_(c) is equal to the number N_(xBLOCK) _(_) _(TI)(n,s).

FIG. 30, including views (a) and (b), illustrates a basic operation of atwisted row-column block interleaver according to an embodiment of thepresent invention.

FIG. 30(a) shows a write operation in the time interleaver, and FIG.30(b) shows a read operation in the time interleaver. A first XFECBLOCKis written column-wise into a first column of a TI memory, and a secondXFECBLOCK is written into a next column, and so on as shown in FIG.30(a). Then, in an interleaving array, cells are read diagonal-wise.During diagonal-wise reading from a first row (rightwards along a rowbeginning with a left-most column) to a last row, N_(r) cells are readout as shown in FIG. 30(b). In detail, assuming z_(n,s,i)(i=0, . . . ,N_(r)N_(c)) as a TI memory cell position to be read sequentially, areading process in such an interleaving array is performed bycalculating a row index R_(n,s,i), a column index C_(n,s,i), and anassociated twisting parameter T_(n,s,i) as in the following Equation.

$\begin{matrix}{{{GENERATE}\mspace{14mu} \left( {R_{n,s,i},C_{n,s,i}} \right)} = \left\{ {{R_{n,s,i} = {{mod}\left( {i,N_{r}} \right)}},{T_{n,s,i} = {{mod}\left( {{S_{shift} \times R_{n,s,i}},N_{c}} \right)}},{C_{n,s,i} = {{mod}\left( {{T_{n,s,i} + \left\lfloor \frac{i}{N_{r}} \right\rfloor},N_{c}} \right)}}} \right\}} & \left\lbrack {{Equation}\mspace{14mu} 8} \right\rbrack\end{matrix}$

Here, S_(shift) is a common shift value for a diagonal-wise readingprocess regardless of N_(xBLOCK) _(_) _(TI)(n,s), and the shift value isdetermined by N_(xBLOCK) _(_) _(TI) _(_) _(MAX) given in PLS2-STAT as inthe following Equation.

                                     [Equation  9]${for}\mspace{14mu} \left\{ {\begin{matrix}{{N_{{xBLOCK\_ TI}{\_ MAX}}^{\prime} = {N_{{xBLOCK\_ TI}{\_ MAX}} + 1}},} & {{{if}\mspace{14mu} N_{{xBLOCK\_ TI}{\_ MAX}}{mod}\; 2} = 0} \\{{N_{{xBLOCK\_ TI}{\_ MAX}}^{\prime} = N_{{xBLOCK\_ TI}{\_ MAX}}},} & {{{if}\mspace{14mu} N_{{xBLOCK\_ TI}{\_ MAX}}{mod}\; 2} = 1}\end{matrix},\mspace{20mu} {S_{shift} = \frac{N_{{xBLOCK\_ TI}{\_ MAX}}^{\prime} - 1}{2}}} \right.$

As a result, cell positions to be read are calculated by coordinatesz_(n,s,i)=N_(r)C_(n,s,i)+R_(n,s,i).

FIG. 31 illustrates an operation of a twisted row-column blockinterleaver according to another embodiment of the present invention.

More specifically, FIG. 31 illustrates an interleaving array in a TImemory for each TI group, including virtual XFECBLOCKs when N_(xBLOCK)_(_) _(TI) (0,0)=3, N_(xBLOCK) _(_) _(TI)(1,0)=6 and N_(xBLOCK) _(_)_(TI)(2,0)=5.

A variable number N_(xBLOCK) _(_) _(TI)(n,s)=N_(r) may be less than orequal to N′_(xBLOCK) _(_) _(TI) _(_) _(MAX). Thus, in order to achievesingle-memory deinterleaving at a receiver side regardless of N_(xBLOCK)_(_) _(TI)(n,s), the interleaving array for use in the twistedrow-column block interleaver is set to a size ofN_(r)×N_(c)=N_(cells)×N′_(xBLOCK) _(_) _(TI) _(_) _(MAX) by insertingthe virtual XFECBLOCKs into the TI memory and a reading process isaccomplished as in the following Equation.

[Equation 10] p = 0; for i = 0; i < N_(cells)N′_(xBLOCK) _(—) _(TI) _(—)_(MAX);i = i + 1 {GENERATE (R_(n,s,i), C_(n,s,i)); V_(i) = N_(r)C_(n,s,j) + R_(n,s,j) if V_(i) < N_(cells)N_(xBLOCK) _(—) _(TI) (n,s) {Z_(n,s,p) = V_(i); p = p + l; } }

The number of TI groups is set to 3. An option of the time interleaveris signaled in the PLS2-STAT data by DP_TI_TYPE=‘0’,DP_FRAME_INTERVAL=‘1’, and DP_TI_LENGTH=‘1’, i.e., NTI=1, IJUMP=1, andPI=1. The number of XFECBLOCKs, each of which has Ncells=30 cells, perTI group is signaled in the PLS2-DYN data by NxBLOCK_TI(0,0)=3,NxBLOCK_TI(1,0)=6, and NxBLOCK_TI(2,0)=5, respectively. A maximum numberof XFECBLOCKs is signaled in the PLS2-STAT data by NxBLOCK_Group MAX,which leads to └N_(xBLOCK) _(_) _(Group) _(_) _(MAX)/N_(TI) ┘=N_(xBLOCK)_(_) _(TI) _(_) _(MAX)=6.

The purpose of the Frequency Interleaver, which operates on datacorresponding to a single OFDM symbol, is to provide frequency diversityby randomly interleaving data cells received from the frame builder. Inorder to get maximum interleaving gain in a single frame, a differentinterleaving-sequence is used for every OFDM symbol pair comprised oftwo sequential OFDM symbols.

Therefore, the frequency interleaver according to the present embodimentmay include an interleaving address generator for generating aninterleaving address for applying corresponding data to a symbol pair.

FIG. 32, including views (a)-(c), illustrates an interlaving addressgenerator including a main pseudo-random binary sequence (PRBS)generator and a sub-PRBS generator according to each FFT mode accordingto an embodiment of the present invention.

FIG. 32(a) shows the block diagrams of the interleaving-addressgenerator for 8K FFT mode, FIG. 32(b) shows the block diagrams of theinterleaving-address generator for 16K FFT mode and FIG. 32(c) shows theblock diagrams of the interleaving-address generator for 32K FFT mode.

The interleaving process for the OFDM symbol pair is described asfollows, exploiting a single interleaving-sequence. First, availabledata cells (the output cells from the Cell Mapper) to be interleaved inone OFDM symbol O_(m,l) is defined as O_(m,l)=[x_(m,l,0), . . . ,x_(m,l,p), . . . , x_(m,l,N) _(data) ⁻¹] for l=0 . . . , N_(sym)−1,where x_(m,l,p) is the p^(th) cell of the l^(th) OFDM symbol in them^(th) frame and N_(data) is the number of data cells: N_(data)=C_(FSS)for the frame signaling symbol(s), N_(data)=C_(data) for the normaldata, and N_(data)=C_(FES) for the frame edge symbol. In addition, theinterleaved data cells are defined as P_(m,l)=[v_(m,l,0), . . . ,v_(m,l,N) _(data) ⁻¹] for l=0, . . . , N_(symb)−1.

For the OFDM symbol pair, the interleaved OFDM symbol pair is given by

v_(m,l,H) _(i) _((p))=x_(m,l,p), p=0, . . . , N_(data)−1, for the firstOFDM symbol of each pair

v_(m,l,p)=x_(m,l,H) _(i) _((p)), p=0, . . . , N_(data)−1, for the secondOFDM symbol of each pair,

where H_(l)(p) is the interleaving address generated by a PRBSgenerator.

FIG. 33, including views (a) and (b), illustrates a main PRBS used forall FFT modes according to an embodiment of the present invention.

FIG. 33(a) illustrates the main PRBS, and FIG. 33(b) illustrates aparameter Nmax for each FFT mode.

FIG. 34, including views (a) and (b), illustrates a sub-PRBS used forFFT modes and an interleaving address for frequency interleavingaccording to an embodiment of the present invention.

FIG. 34(a) illustrates a sub-PRBS generator, and FIG. 34(b) illustratesan interleaving address for frequency interleaving. A cyclic shift valueaccording to an embodiment of the present invention may be referred toas a symbol offset.

FIG. 35 illustrates a write operation of a time interleaver according toan embodiment of the present invention.

FIG. 35 illustrates a write operation for two TI groups.

A left block in the figure illustrates a TI memory address array, andright blocks in the figure illustrate a write operation when two virtualFEC blocks and one virtual FEC block are inserted into heads of twocontiguous TI groups, respectively.

Hereinafter, description will be given of a configuration of a timeinterleaver and a time interleaving method using both a convolutionalinterleaver (CI) and a block interleaver (BI) or selectively usingeither the CI or the BI according to a physical layer pipe (PLP) mode. APLP according to an embodiment of the present invention is a physicalpath corresponding to the same concept as that of the above-describedDP, and a name of the PLP may be changed by a designer.

A PLP mode according to an embodiment of the present invention mayinclude a single PLP mode or a multi-PLP mode according to the number ofPLPs processed by a broadcast signal transmitter or a broadcast signaltransmission apparatus. The single PLP mode corresponds to a case inwhich one PLP is processed by the broadcast signal transmissionapparatus. The single PLP mode may be referred to as a single PLP.

The multi-PLP mode corresponds to a case in which one or more PLPs areprocessed by the broadcast signal transmission apparatus. The multi-PLPmode may be referred to as multiple PLPs.

In the present invention, time interleaving in which different timeinterleaving schemes are applied according to PLP modes may be referredto as hybrid time interleaving. Hybrid time interleaving according to anembodiment of the present invention is applied for each PLP (or at eachPLP level) in the multi-PLP mode.

FIG. 36 illustrates an interleaving type applied according to the numberof PLPs in a table.

In a time interleaving according to an embodiment of the presentinvention, an interleaving type may be determined based on a value ofPLP_NUM. PLP_NUM is a signaling field indicating a PLP mode. WhenPLP_NUM has a value of 1, the PLP mode corresponds to a single PLP. Thesingle PLP according to the present embodiment may be applied only to aCI.

When PLP_NUM has a value greater than 1, the PLP mode corresponds tomultiple PLPs. The multiple PLPs according to the present embodiment maybe applied to the CI and a BI. In this case, the CI may performinter-frame interleaving, and the BI may perform intra-frameinterleaving.

FIG. 37 is a block diagram including a first example of a structure of ahybrid time interleaver described above.

The hybrid time interleaver according to the first example may include aBI and a CI. The time interleaver of the present invention may bepositioned between a BICM chain block and a frame builder.

The BICM chain block illustrated in FIGS. 37 and 38 may include theblocks in the processing block 5000 of the BICM block illustrated inFIG. 19 except for the time interleaver 5050. The frame builderillustrated in FIGS. 37 and 38 may perform the same function as that ofthe frame building block 1020 of FIG. 18.

As described in the foregoing, it is possible to determine whether toapply the BI according to the first example of the structure of thehybrid time interleaver depending on values of PLP_NUM. That is, whenPLP_NUM=1, the BI is not applied (BI is turned OFF) and only the CI isapplied. When PLP_NUM>1, both the BI and the CI may be applied (BI isturned ON). A structure and an operation of the CI applied whenPLP_NUM>1 may be the same as or similar to a structure and an operationof the CI applied when PLP_NUM=1.

FIG. 38 is a block diagram including a second example of the structureof the hybrid time interleaver described above.

An operation of each block included in the second example of thestructure of the hybrid time interleaver is the same as the abovedescription in FIG. 37. It is possible to determine whether to apply aBI according to the second example of the structure of the hybrid timeinterleaver depending on values of PLP_NUM. Each block of the hybridtime interleaver according to the second example may perform operationsaccording to embodiments of the present invention. In this instance, anapplied structure and operation of a CI may be different between a caseof PLP_NUM=1 and a case of PLP_NUM>1.

FIG. 39 is a block diagram including a first example of a structure of ahybrid time deinterleaver.

The hybrid time deinterleaver according to the first example may performan operation corresponding to a reverse operation of the hybrid timeinterleaver according to the first example described above. Therefore,the hybrid time deinterleaver according to the first example of FIG. 39may include a convolutional deinterleaver (CDI) and a blockdeinterleaver (BDI).

A structure and an operation of the CDI applied when PLP_NUM>1 may bethe same as or similar to a structure and an operation of the CDIapplied when PLP_NUM=1.

It is possible to determine whether to apply the BDI according to thefirst example of the structure of the hybrid time deinterleaverdepending on values of PLP_NUM. That is, when PLP_NUM=1, the BDI is notapplied (BDI is turned OFF) and only the CDI is applied.

The CDI of the hybrid time deinterleaver may perform inter-framedeinterleaving, and the BDEI may perform intra-frame deinterleaving.Details of inter-frame deinterleaving and intra-frame deinterleaving arethe same as the above description.

A BICM decoding block illustrated in FIGS. 39 and 40 may perform areverse operation of the BICM chain block of FIGS. 37 and 38.

FIG. 40 is a block diagram including a second example of the structureof the hybrid time deinterleaver.

The hybrid time deinterleaver according to the second example mayperform an operation corresponding to a reverse operation of the hybridtime interleaver according to the second example described above. Anoperation of each block included in the second example of the structureof the hybrid time deinterleaver may be the same as the abovedescription in FIG. 39.

It is possible to determine whether to apply a BDI according to thesecond example of the structure of the hybrid time deinterleaverdepending on values of PLP_NUM. Each block of the hybrid timedeinterleaver according to the second example may perform operationsaccording to embodiments of the present invention. In this instance, anapplied structure and operation of a CDI may be different between a caseof PLP_NUM=1 and a case of PLP_NUM>1.

FIG. 41 illustrates an application-related broadcast service accordingto an embodiment of the present invention.

The present invention proposes a signaling scheme and a synchronizationscheme in a broadcast service related to an application among theabove-described broadcast services. Here, the application-relatedbroadcast service may refer to a broadcast service corresponding to acase in which provision of a basic broadcast service is related to anapplication. Specifically, examples thereof may include a linear serviceincluding application-based enhancements and/or a standaloneapplication-based service. According to a given embodiment, thesignaling scheme of the present invention may be applied to another formof service which uses an application.

First, a description will be given of the linear service includingapplication-based enhancements. Here, the linear service may refer to ageneral broadcast service. An enhancement may refer to an enhancementservice or an interactive service which delivers additional informationfor a general broadcast service. In addition, application-basedenhancement may refer to a case in which the above-described additionalinformation is provided and/or controlled based on an application.

For example, a case, in which a player information application providesinformation about football players (application-based enhancement) whena football game (general broadcast service) is broadcast, may correspondto the linear service including application-based enhancements.

The standalone application-based service will be described. Thestandalone application-based service may refer to a broadcast serviceonly including an application-based enhancement. In other words, a casein which an application provides a service rather than theapplication-based enhancement provides additional information to thebasic broadcast service may correspond to the standaloneapplication-based service. A broadcast-independent application, etc. maybe an example of an application that provides the standaloneapplication-based service.

The application-based enhancement may include several components. Thecomponents of the application-based enhancement may include one or moreapplications, zero or more activation notifications, zero or moreadditional non-real-time (NRT) content items and/or zero or moreon-demand items.

Here, each application may correspond to an NRT content item which canbe executed in an application run time environment. Here, actions to beperformed by applications may be initiated by notifications deliveredthrough a broadcast network/broadband network, and these notificationsmay correspond to the above-described activation notifications. Thesenotifications may be referred to as “events”. Here, the additional NRTcontent items and/or the on-demand items may refer to data to be used byan application.

According to a given embodiment, one of applications included in theapplication-based enhancement may be set as a primary application. Whenthe primary application is present, the primary application may beexecuted upon selecting a broadcast service including theapplication-based enhancement. Applications other than the primaryapplication may be executed by signaling through the broadcastnetwork/broadband network. Alternatively, applications other than theprimary application may be executed by other applications which havebeen executed. In this case, the applications other than the primaryapplication may be executed by createApplication( ) of JavaScript.

As described in the foregoing, the present invention proposes asignaling scheme for various types of application-based enhancements. Inaddition, the present invention proposes a scheme of delivering anactivation notification in synchronization with a time base. Actions ofan application may be synchronized by the synchronized activationnotification.

Here, the application may refer to a set of documents (HTML, CSS,JavaScript, etc.) included in an enhancement/interactive service.

Here, a content item may refer to a set of one or more files intended tobe treated as one unit for presentation by a service provider.

Here, an event may refer to a timed notification that indicates anaction to be performed in a DASH client or application.

Here, an event stream may refer to a stream of the above-describedevents.

Here, the NRT content item may refer to a content item delivered aheadof time for another use in a future presentation or application.

Here, an on-demand content item may refer to a content item downloadedand presented at a point in time requested by a user.

FIG. 42 illustrates a part of an ApplicationList element according to anembodiment of the present invention.

FIG. 43 illustrates another part of the ApplicationList elementaccording to an embodiment of the present invention.

Even though the two figures originally corresponded to one figure, theone figure is divided into two figures due to space constraints.

As described in the foregoing, the broadcast service may include zero ormore application-based enhancements. For example, the linear service mayinclude an application-based enhancement having one application which isexecuted in the background to manage insertion of a targetedadvertisement. In addition, the linear service may further include anapplication-based enhancement having a set of applications which providean interactive viewing experience related to an audio/video program.

Here, each of the application-based enhancements may be separatelysignaled. Therefore, manufacturers who manufacture various applicationsmay not cooperate with each other in signaling thereof.

A set of applications included in one application-based enhancement maybe signaled by an application signaling table (AST). The AST is one ofXML documents, and may include the ApplicationList element as a rootelement. One AST may include signaling information of applicationsincluded in one application-based enhancement. According to a givenembodiment, one AST may be extended to signal a plurality ofapplication-based enhancements.

Service signaling information of one service may include an AST for eachapplication-based enhancement included in the service. In other words,when one service includes a plurality of application-based enhancements,service signaling information of the service may include a plurality ofASTs.

An example of the AST illustrated in the figure will be described.According to a given embodiment, each element/attribute of the AST maybe added/omitted/changed.

The AST may include the ApplicationList element as a root element. TheApplicationList element may include a list of Application elements. Thatis, the ApplicationList element may include at least one or moreApplication elements.

Each of the Application elements may include an appName element, anapplicationDescriptor element, an applicationSpecificDescriptor element,an applicationUsageDescriptor element, an applicationBoundary element,an applicationTransport element, an applicationLocation element, anatsc:Capabilities element, an atsc:liveEventSource element, anatsc:ContentItems element, an @applicationIdentifier attribute, an@atsc:serviceId attribute and/or an @atsc:protocolVersion attribute.

The appName element may indicate a name of an application which isindicated by the Application element. This element may be omitted. Theapplication name may be expressed in various languages. The appNameelement may further include an @lang attribute. The @lang attribute mayindicate a language of the application name.

The applicationDescriptor element may include information of thecorresponding application. The applicationDescriptor element may includeinformation which can be commonly included in all applications. TheapplicationDescriptor element may include an icon element, an @typeattribute, an @controlCode attribute, an @visibility attribute, an@serviceBound attribute, an @priority attribute, an @version attribute,an @mhpVersion attribute, an @storageCapabilities attribute and/or an@trickModeTolerance attribute.

The icon element may indicate an icon which can be used to represent thecorresponding application. This element may be omitted. The icon elementmay include an @mimeType attribute that indicates a MIME type of anapplication image (icon) and/or an @width/@height/@depth attribute thatindicates a width/height/depth of the application image using pixels.The icon element may further include an @url attribute having HTTP URLinformation for downloading the application image.

The @type attribute may indicate a type of the correspondingapplication. For example, this attribute may indicate that thecorresponding application is an application according to ATSC or DVB.

The @controlCode attribute may include information for controlling astate of the corresponding application. For example, this attribute mayhave information about autolaunch, kill, etc. The state of thecorresponding application may be controlled using the information.

The @visibility attribute may indicate whether the correspondingapplication is visible to a user and/or another application. Here, in abroad sense, whether the corresponding application is visible to theuser and/or the other application may indicate whether the correspondingapplication appears in a user interface. This attribute may indicatewhether the corresponding application is audible or sensible in additionto whether the corresponding application is visible. According to agiven embodiment, whether the corresponding application is audible tothe user, etc. through a speaker may be indicated by separately settingan @audibility attribute. This attribute may be omitted.

The @serviceBound attribute may indicate whether the correspondingapplication is service-bounded. The corresponding application may beservice-bounded when this attribute is set to true, and may not beservice-bounded when this attribute is set to false. This attribute mayhave the true value as a default value. This attribute may be omitted.When this attribute is omitted, it may mean that the correspondingapplication is service-bounded.

The @priority attribute may indicate a relative priority of thecorresponding application when compared to other applications. The@version attribute may indicate a version of the correspondingapplication. The @mhpVersion attribute may indicate a platform or aversion necessary for the corresponding application. This attribute maybe omitted.

The @storageCapabilities attribute may indicate the amount of storagenecessary to cache the corresponding application. This attribute may beomitted. According to a given embodiment, this attribute may be used toindicate whether the corresponding application can be cached.

The @trickModeTolerance attribute may indicate whether the correspondingapplication is compatible with a certain trick mode. Compatibility mayrefer to whether the corresponding application can tolerate the certaintrick mode when the certain trick mode is executed. Examples of thetrick mode may include pause, FF, slow mode, rewind, etc. This attributemay be omitted. In a broadcast service having an applicationenhancement, when the user performs a trick play for the broadcastservice, signaling may be performed such that a basic program subjectedto the trick play can be normally enhanced.

The applicationSpecificDescriptor element may have necessary informationonly for a certain type of application unlike the above-describedapplicationDescriptor element. That is, information of this element maybe subject to an application type. This element may be unnecessaryaccording to application type, and thus this element may be omitted.

The applicationUsageDescriptor element may indicate a function of thecorresponding application. For example, this element may indicate thatthe corresponding application can be used for teletext. This element maybe unnecessary according to application type. This element may beomitted.

The applicationBoundary element may indicate URL information thatdefines extension of an application boundary of the correspondingapplication. This element may be omitted.

The applicationTransport element may indicate a protocol used to deliverthe corresponding application. For example, this element may indicatethat the corresponding application is delivered through ROUTE, MMT orHTTP. According to a given embodiment, this element may indicate aprotocol used when the AST is delivered. According to theabove-described method of delivering service data of the presentinvention, permissible values of this element may correspond to ROUTE,MMT, HTTP, etc.

The applicationLocation element may indicate a URL that provides alocation at which the corresponding application can to be acquired.According to a given embodiment, this element may indicate a URL atwhich the corresponding application can to be acquired.

The atsc:Capabilities element may indicate capability information formeaningfully processing the corresponding application/application-basedenhancement. Here, capability for meaningful processing may refer tocapability of a receiving side capable of meaningfully performingrendering/decoding/reproduction, etc. According to a given embodiment,the capability information may be indicated by a preset capability code.

The atsc:liveEventSource element may provide information for receivingthe above-described event in a live situation. For example, in a livebroadcast program, an event needs to be changed in real time anddelivered in order to provide an enhancement according to content of thebroadcast program which changes in real time. Unlike pre-producedcontent, the above-described operation may be needed in the livesituation. This element may provide information such as a URL, etc. forreceiving the event in real time in this situation. This element mayinclude an @url attribute, an @shortPollingPeriod attribute and/or an@targetDevice attribute.

The @url attribute may indicate a URL for receiving the event in thelive situation. The @shortPollingPeriod attribute may indicate a pollingperiod when the event is acquired in short polling of a broadbandnetwork. The @targetDevice attribute may indicate a device targeted bythe live event. For example, a primary device (PD) or a companion device(CD) may correspond to the target device. The @shortPollingPeriodattribute and/or the @targetDevice attribute may be omitted.

The atsc:ContentItems element may include information about each contentitem to be used by the corresponding application. The number ofContentItems elements may correspond to the number of respective contentitems. The atsc:ContentItems element may further include a locationelement, an @ContentLinkage attribute, an @updatesAvailable attribute,an @TFAvailable attribute, an @contentSecurityCondition attribute, an@availablelnBroadcast attribute, an @availableOnInet attribute, an@playbackLengthInSeconds attribute, an @playbackDelay attribute, an@expiration attribute, an @size attribute, an @name attribute and/or atimeSlotInfo element.

The location element may indicate information about a location at whichthe content item can be acquired. This information may have a form ofURL according to a given embodiment. The location element may beomitted, or a plurality of location elements may be present.

The @ContentLinkage attribute may indicate an application in which thecontent item is to be used. Signaling by a certain application may beperformed using a value of this attribute and information about eventsto be described below (EventStream element, emsg box, etc.). Forexample, this attribute may provide an application identifier for thecertain application or indicate a certain LCT session in whichapplication data thereof is delivered.

The @updatesAvailable attribute may indicate whether the content itemcan be updated. This attribute may have a value of true or false. The@TFAvailable attribute may indicate whether a text fragment is presenton a signaling channel for the content item.

The @contentSecurityCondition attribute may indicate a security state ofthe content item. The @availablelnBroadcast attribute may indicatewhether the content item can be acquired through a broadcast network.The @availableOnInet attribute may indicate whether the content item canbe acquired through an Internet protocol network.

The @playbackLengthInSeconds attribute may indicate a length in secondsof the content item when the content item is reproduced. This attributemay be omitted. The @playbackDelay attribute may indicate a reproductiondelay of the content item. This attribute may be omitted. The@expiration attribute may indicate an expiration period of the contentitem. This attribute may be omitted. The @size attribute may indicate asize of the content item. This attribute may be omitted. The @nameattribute may indicate a name of the content item. This attribute may beomitted.

The timeSlotInfo element may include time slot-related information ofthe content item. The timeSlotInfo element may further include an@time_slot_start attribute, an @time_slot_length attribute, an@acquisition_time attribute, an @repeat_period attribute and/or an@slot_count attribute.

The @time_slot_start attribute may indicate a start time of a time slot.This time may be expressed in GPS seconds from 00:00:00 UTC of Jan. 6,1980. When this field has a value of 0, this field may indicate that thetime slot starts from an uncertain past.

The @time_slot length attribute may indicate a length in minutes of thetime slot.

The @acquisition_time attribute may indicate a minimum time intervallength in which transmission of at least one content item is ensured.This time interval may be expressed in minutes. Here, this time intervalis presumed to start from an arbitrary time in the time slot and mayinclude an end of the time slot. When one large content item isrepeatedly transmitted during the time slot, this attribute maycorrespond to a time taken when one instance of the content item istransmitted. When a plurality of small content items is transmitted in acarousel, this attribute may correspond to a cycle time of the carousel.

The @repeat_period attribute may indicate a repetition interval inminutes of the time slot.

The @slot_count attribute may indicate the number of times at which thetime slot occurs. The number of times may be indicated from a time slotwhich starts from a time indicated by the @time_slot_start attribute.When this attribute has a value of 0, repetition may be presumed toindefinitely continue.

The Application element may directly include the @ContentLinkageattribute and/or the timeSlotInfo element. That is, the @ContentLinkageattribute and/or the timeSlotInfo element may be included in both theApplication element and the atsc:ContentItems element.

Among the attributes of the Application element, the@applicationIdentifier attribute may indicate an identifier of theapplication. This value may be a globally unique value.

The @atsc:serviced attribute may indicate a service identifier of aservice related to the corresponding application.

The @atsc:protocolVersion attribute may indicate a protocol version ofthe corresponding application. According to a given embodiment, thecorresponding field may be divided into two fields indicating a majorprotocol version and a minor protocol version. Alternatively, this fieldmay simultaneously provide the major/minor protocol versions.

The ApplicationList element may include an @ASTVersionNumber attribute,an @timeSpanStart attribute and/or an @timeSpanLength attribute inaddition to the plurality of Application elements.

The @ASTVersionNumber attribute may indicate a version number of thewhole corresponding AST. According to a given embodiment, thecorresponding field may be divided into two fields indicating a majorprotocol version and a minor protocol version. Alternatively, this fieldmay simultaneously provide the major/minor protocol versions.

The @timeSpanStart attribute may indicate a start of a time intervalcovered by a corresponding AST instance. The AST may be divided into aplurality of instances and transmitted. Each of the AST instances mayinclude signaling information for each time interval.

The @timeSpanLength attribute may indicate a length of a time intervalcovered by a corresponding AST instance. It is possible to calculate thetime interval covered by the corresponding AST instance together with avalue of the @timeSpanStart attribute.

The respective fields of the AST according to the above-describedembodiments may be omitted or changed. In addition, according to a givenembodiment, additional fields may be added to the AST. The respectivefields of the AST may be replaced by fields having the same/similarmeanings.

The above-described AST may be transmitted through a broadcast networkor a broadband network.

When the AST is transmitted through the broadcast network, an AST for anapplication enhancement may be delivered through a service signalingchannel of a broadcast service to which the application enhancement isrelated. Here, the service signaling channel of the service may refer toa path through which the above-described SLS is delivered. For example,in ROUTE, an LCT transmission session specified by tsi=0 may deliver theAST as a dedicated signaling channel. In MMT, an MMTP packet flowspecified by packet_id=00 may deliver the AST as a dedicated signalingchannel.

When the AST is delivered through the broadband network, the AST may beacquired through a query. This query may be generated using base URLinformation in the SLT described above. The base URL may correspond toURL information for acquiring the AST. Here, the SLT may correspond toan SLT including bootstrap information for a broadcast service relatedto the AST. In a scenario in which a watermark is used, the base URL maybe acquired through the watermark or through an auto content recognition(ACR) process using the watermark.

FIG. 44 illustrates an event message table (EMT) according to anembodiment of the present invention.

As described in the foregoing, actions to be performed by applicationsmay be initiated by notifications delivered through the broadcastnetwork/broadband network. These notifications may be referred to as“events”. According to context, operations, actions, or operated statesof the applications initiated by the notifications may be referred to as“events”. In addition, executable actions of the applications may bereferred to as “events”.

These events may be delivered through the broadcast network or thebroadband network. In this case, each event or an action performed bythe event may need to be synchronized with a basic broadcastservice/broadcast program. The present invention proposes a deliveryscheme and a synchronization scheme of the event.

A description will be given of a case in which the event is deliveredthrough the broadcast network.

When the event is delivered through the broadcast network, the event maybe delivered as a DASH event. In this instance, the event may bedelivered in the form of an EventStream element or an emsg box. A casein which the event is delivered through the EventStream element maycorrespond to a case in which the event is delivered as a form of anEventStream element which appears in a Period element of an MPD. A casein which the event is delivered in the form of the emsg box maycorrespond to a case in which the event is delivered through an emsg boxwhich appears in representation segments.

The two event delivery mechanisms may be interchangeable. For example,one event stream may include several events delivered through theEventStream element and/or other events delivered through the emsg box.

The events delivered through the EventStream element may correspond toevents to be delivered to the receiving side during a time intervalcorresponding to a certain period. In other words, the MPD may providesignaling information at time intervals of a service referred to as aperiod as service signaling information of a certain service. Thesignaling information for the period is included in an MPD Periodelement, and this Period element may include the EventStream element.The EventStream element may provide signaling (event) necessary foroperations of applications during the period of the service.

The EventStream element may correspond to a list of Event elements. EachEventStream element may have a schemeldUri attribute and/or a valueattribute. These two attributes may indicate types of events in anEventStream. According to a given embodiment, these two attributes mayidentify events. Here, predefined values may be used as values of theschemeldUri attribute and/or the value attribute. Alternatively, aservice provide may additionally define and use values of theschemeldUri attribute and/or the value attribute. An “owner” of theschemeldUri attribute needs to uniquely define the schemeldUriattribute, and needs to define semantics of the event and the valueattribute. Value information may be subject to an application and usedto identify a certain event stream in one service.

The EventStream element may further include a timescale attribute. Thisattribute may indicate a reference time scale in duration and an eventpresentation time.

Each Event sub-element of the EventStream element may include apresentationTime attribute, a duration attribute, and/or an idattribute. The presentationTime attribute may indicate a start time ofeach event, the duration attribute may indicate a duration of eachevent, and the id attribute may indicate an identifier of each event. Inthis context, the event may refer to an action of an applicationinitiated by a notification or a phenomenon caused by the action (pop-upwindow, etc.).

The Event sub-element may not have data for the corresponding event.However, according to a given embodiment, an Event element may have anadditional data element or attribute. This data element/attribute mayprovide data necessary to execute an action initiated by the event.

According to a given embodiment, a plurality of EventStream elementshaving different types may be present in one period.

When the event is delivered in the form of the emsg box, the event maybe delivered through the emsg box which appears in the Representationsegments as described in the foregoing. In this instance, anInbandEventStream element of the Representation of the MPD may signalwhether an event is present in the emsg box in the segments.

An InbandEvent element may include schemeldUri and/or value. These twofields may indicate a type of an event in the emsg box. According to agiven embodiment, these two fields may be used to identify the event.

The InbandEvent element may further include a timescale field. Thisfield may indicate a reference time scale related to an event.

In addition, the InbandEvent element may further includepresentation_time_delta information, event duration information and/orid information. The presentation_time_delta information may indicate astart time of the corresponding event. Here, the start time may beexpressed by a relative value with respect to a start time of theRepresentation. The event_duration information may indicate a durationof the corresponding event. The id information may identify an instanceof the corresponding event.

The InbandEvent element may further optionally include message_datainformation. The message_data information may provide data necessary toexecute an action which is initiated by the corresponding event.

A description will be given of a case in which the event is deliveredthrough the broadband network.

Batch delivery using a batch through MPD and incremental delivery usingthe emsg box have been described with regard to delivery of the eventthrough the broadcast network. Similarly, batch delivery and incrementaldelivery may be proposed with regard to delivery of the event throughthe broadband network.

When the event is delivered using batch delivery through the broadbandnetwork, events may be delivered through an event stream table (EST).This EST may be referred to as an EMT according to a given embodiment.As an XML document, the EST may include an EventStreamTable element as aroot element.

The EventStreamTable element may correspond to a list of EventStreamelements. Each of the EventStream elements may be identical to theEventStream element in delivery of the event through the broadcastnetwork described above. The list of EventStream elements may includeall event streams for one service.

The illustrated EMT is an EMT (EST) according to another embodiment ofthe present invention. The EMT may include an @mpdId attribute, an@periodId attribute, and an EventStream element.

The @mpdId attribute may correspond to an identifier of an MPD relatedto events described by the EMT. The MPD may be used as a time referenceof the corresponding events.

The @periodId attribute may correspond to an identifier of a period ofthe MPD related to the events of the EMT. The period may be used as atime reference of the corresponding events.

Respective fields in the EventStream element are as described above.Here, each Event element may have a value suitable for a type thereofaccording to a value of @schemeIdURi and/or @value. An @presentationTimeattribute indicates a start time of an event as a relative value withrespect to a start time of a period, and this period may correspond to aperiod identified by the @mpdId and @periodId attributes.

The EST may be acquired through a query as described above. The querymay be generated by base URL information in the SLT. A descriptionthereof has been given above.

When events are delivered using incremental delivery through thebroadband network, the events may be separately delivered through a liveevent server. Polling may be periodically performed using the live eventserver. When an event to be transmitted in the corresponding period ispresent, the event server may deliver the event to a receiver.Information such as a URL, a polling period, etc. of the live eventserver may have been delivered to the receiver by the above describedAST or EST, or another signaling object.

The event delivered in this case may have the same format as a format ofthe emsg box in the above-described delivery of the event using the emsgbox. According to a given embodiment, signaling informationcorresponding to the above-described InbandEvent element may bedelivered together with the live event.

SchemeldUri information and value information may correspond totargetURI and eventName arguments in an API for addition and deletion ofa stream event listener for an event stream. The events according to therespective embodiments described above may further include an optionaldata attribute. The data attribute may provide data used to execute anaction which is initiated by the corresponding event. The data attributemay correspond to a data attribute of a StreamEvent interface returnedto a registered listener when the event occurs.

In delivery of an NRT content item, an NRT delivery method of ATSC maybe used. However, in this case, an AST is used instead of an NRT-IT, anda content item to be delivered by the AST may be identified. Inaddition, an application may initiate broadband delivery of the NRTcontent item even when the NRT content item is not listed in the AST.

An on-demand content item may be delivered through the broadbandnetwork.

Broadband delivery of the on-demand content item may be initiated by anapplication.

Synchronization of an application will be described.

The application may need to be synchronized in several aspects. Forexample, actions of the application may need to be synchronized with ascheduled audio/video service. In addition, the application may need tobe initiated and suspended according to the scheduled audio/videoservice. The application and the actions of the application may need tobe synchronized with reproduction of recorded content, NRT content, etc.in addition to a basic broadcast service. In addition, the applicationmay need to be initiated or suspended according to recorded content, NRTcontent, etc. to effectively enhance user experience.

In addition, an application in a CD may need to be synchronized withaudio/video content reproduced in a PD such that an applicationenhancement provided by the CD can be effectively synchronized andprovided.

User experience will be described.

According to a given embodiment, the user may control operations of theapplication for an efficient application enhancement since theenhancement may hinder viewing when the operations cannot be controlled.As an embodiment, permission of the user may be used. The user maycollectively permit all services or some particular services.Alternatively, the user may permit applications of the respectiveservices or the services case by case.

When the user gives permission case by case, an application notificationmay need to be displayed first before the application is activated.Through this notification, the application may obtain to be activatedpermission from the user. The application may be in a blocked stateuntil obtaining permission.

A format and a location of the notification for this permission may bedetermined by a device manufacturer. An actual user interface forpermission may be determined by the device manufacturer. Referring tothese issues, a certain format, etc. may be proposed by a certain entityfrom an industrial viewpoint.

A notification for permission may time-out or be dismissed by the user.In this way, even when the user does not immediately determine whetherto permit activation of the application, the user may be prevented frombeing hindered from viewing continuously by this notification. Even whenthe notification is on a time-out or dismissed and thus is invisible,the user may activate or block the application through setting, etc. Theuser may terminate the activated application. In this case, even when asignal for activating the application is received, the application maybe continuously blocked.

A description will be given of synchronization of an action and anaction parameter.

Download of the application, activation of the application, terminationof the application, and/or a certain action of the application may needto be synchronized with a basic broadcast program, etc.

With regard to actions of the application, action parameters may beneeded to perform the actions. The actions may be performed usinginformation of the parameters. Examples of the action parameters mayinclude an application identifier parameter for identifying anapplication related to an action, a time parameter that indicates a timeat which an action is to be performed, and/or a synchronization levelparameter related to a synchronization level of an action. Here, thetime parameter may indicate a start time of an action as a relativevalue with respect to a time base or a media time line. Here, thesynchronization level parameter may indicate a synchronization levelsuch as program level sync, sync less than two seconds, lip sync, framesync, etc.

With regard to an action related to download of the application, thisaction may include an action parameter related to a target device and/oran action parameter related to a jitter interval. The action parameterrelated to the target device may include information as to whether thedownloaded application is for a PC or a CD. The action parameter relatedto the jitter interval may include information related to the jitterinterval for fetching of the application.

With regard to an action related to start of the application, thisaction may include an action parameter related to a target device and/oran action parameter related to a jitter interval. The action parameterrelated to the target device may include information as to whether thestarted application is for a PC or a CD.

As described in the foregoing, examples of the action parameters mayinclude an action parameter that provides data necessary to execute theapplication. This action parameter may include data necessary to performthe corresponding action.

FIG. 45 illustrates a method of providing the broadcast service by thetransmitting side according to an embodiment of the present invention.

The method of providing the broadcast service by the transmitting sideaccording to the present embodiment may include generating service dataand service signaling information, generating a service list table,processing a streaming component, an enhancement component, the servicesignaling information, and/or the service list table in transmissionpackets, generating link layer packets, and/or physically processing thelink layer packets to generate and transmit a broadcast signal.

First, a first mode of a transmitting side may generate the service dataof the broadcast service and the service signaling information forsignaling the service data. Here, the service data may include astreaming component having data related to real-time content of thebroadcast service and/or an enhancement component having data related tothe application-based enhancement of real-time content.

The streaming component may have data necessary to reproduce real-timecontent. For example, the streaming component may correspond to a videocomponent, an audio component, or a closed captioning component. Asdescribed in the foregoing, the application-based enhancement mayprovide an interactive viewing experience for the broadcast service. Asdescribed in the foregoing, the application-based enhancement mayprovide an interactive service through an application for a broadcastprogram, etc. The enhancement component may include data for providingthe application-based enhancement. The enhancement component maycorrespond to the application, and may correspond to a data/content itemfor using the application. Here, the enhancement component maycorrespond to an NRT component and be delivered through the ROUTEprotocol, etc.

In addition, the service may further include a plurality of servicecomponents. Here, the service signaling information may refer to theabove-described SLS.

A second module of the transmitting side may generate the service listtable. The service list table may correspond to the above-described SLT.The SLT may include bootstrap information that indicates a transmissionsession in which the SLS is delivered. Here, the transmission sessionmay correspond to a ROUTE session or an MMTP session. The bootstrapinformation may refer to an IP address, a UDP port number, etc. of theROUTE session or the MMTP session. The first module and the secondmodule may correspond to modules serving as service providers whichmanage generation of a service.

A third module of the transmitting side may process a streamingcomponent, an enhancement component, the service signaling information,and/or the service list table in transmission packets. This step maycorrespond to a step for UDP/IP-processing the service component data,the SLS, and the SLT and encapsulating the service component data, theSLS, and the SLT in an IP packet in order to deliver the service datathrough a broadcast network. Here, a transmission packet may correspondto an IP packet. Here, it is presumed that an FIC is not used and theSLT is encapsulated in the IP packet and delivered through a PLP. Thethird module may correspond to a hardware module that manages a UDP/IPlayer.

A fourth module of the transmitting side may perform link layerprocessing on transmission packets to output at least one link layerpacket. Link layer processing has been described above. Here, the fourthmodule may correspond to a module that performs an operationcorresponding to a link layer. The fourth module may perform headercompression/overhead reduction or packet encapsulation.

A fifth module of the transmitting side may physically process the atleast one link layer packet. The fifth module may correspond to a modulethat manages operation of a physical layer. The fifth module maygenerate BB packets from the link layer packet and perform encoding, bitinterleaving, constellation mapping, etc. on the BB packets. Thereafter,it is possible to perform time interleaving, frame building, frequencyinterleaving, etc., and then a modulation process according to an OFDMscheme. In addition, the fifth module may transmit a broadcast signalincluding physically processed data. Here, the fourth module may beincluded in the fifth module. The fourth and fifth modules may bereplaced by one integrated module. The fifth module may include aplurality of internal blocks. The fourth module may be included in oneof the blocks of the fifth module.

In the method of providing the broadcast service by the transmittingside according to the present embodiment, the service signalinginformation may include an AST that signals applications which providethe application-based enhancement. The AST has been described above. Asdescribed in the foregoing, the AST may be delivered together with theSLS for the broadcast service. In other words, the AST may be deliveredthrough the ROUTE/LCT session in which the SLS is delivered. Accordingto a given embodiment, the AST may be delivered through a broadbandnetwork, etc. In this case, the AST may be requested using URLinformation of the SLT.

In addition, in the present embodiment, the enhancement component maycorrespond to an NRT component of the broadcast service. As described inthe foregoing, the enhancement component may include a relatedapplication or content item with respect to an application enhancementfor the broadcast service.

In a method of providing the broadcast service by the transmitting sideaccording to another embodiment of the present invention, the servicesignaling information may include a user service bundle description(USBD), a service-based transport session instance description (S-TSID),and/or a media presentation description (MPD). As described in theforegoing, the USBD may include URI information for referencing theS-TSID and/or URI information for referencing the MPD. The S-TSID mayinclude transmission session description information related to atransmission session in which a streaming component and an enhancementcomponent of the broadcast service are delivered. The S-TSID may provideinformation about an LCT session in which service components of acertain service are delivered. Examples of this information may includetsi information and/or IP/UDP information of a ROUTE session. The MPDmay include reproduction-related information of the streaming componentof the broadcast service. The MPD may provide description informationfor reproducing DASH representation, etc. included in video and audiocomponents. In other words, the MPD may provide segment URL informationof service components and context information of media segments.

In a method of providing the broadcast service by the transmitting sideaccording to another embodiment of the present invention, the AST mayinclude application elements including information about applicationswhich provide an application-based enhancement. The AST may includeapplication elements as in the above-described embodiment. Theseapplications may be used to provide the application enhancement. Therespective application enhancement may include content item elementsincluding information about content items used by the applications.Content item elements may be present as child elements of theapplication elements described above. The respective content itemelements may describe content items used by the application. At leastone content item element may describe a content item included in anenhancement component. The above-described enhancement component mayhave a certain content item used by a certain application. This contentitem may be described by the AST. In this way, the application-basedenhancement may be provided using the content items acquired through theAST.

In a method of providing the broadcast service by the transmitting sideaccording to another embodiment of the present invention, the S-TSID mayinclude transmission session identifier information that indicates atransmission session in which an enhancement component is delivered. TheS-TSID may indicate a transmission session in which an enhancementcomponent corresponding to an NRT component is delivered. Tsiinformation may be provided to indicate the transmission session.Depending on cases, IP/UDP information for identifying a ROUTE sessionmay be provided. A reception system may acquire enhancement componentsfor providing an application-based enhancement through the S-TSID. Atleast one content item element of the AST may further include contentlink information, and the content link information may be used toindicate an application which uses a content item included in theenhancement component. As described in the foregoing, an @ContentLinkageattribute may be included in a lower element of an application elementand/or a content item element of the AST. This attribute may be used toindicate an application in which the content item delivered in theenhancement component is used. This attribute may be used to connect theAST to the content item. Alternatively, this attribute may be used toconnect the AST to the application. In this way, the content itemacquired using the S-TSID may be used to provide the application-basedenhancement in connection with the application.

In a method of providing the broadcast service by the transmitting sideaccording to another embodiment of the present invention, the MPD mayfurther include a period element that describes reproduction-relatedinformation of a certain interval of real-time content. In apresentation of media content, a period is a concept corresponding to apart obtained by dividing the presentation in terms of time, and theperiod element may provide media reproduction description informationcorresponding to the part. As described in the forgoing, the periodelement may have an event stream element. This event stream element mayinclude a plurality of event elements. These event elements may includeinformation about events that signal actions to be performed by anapplication. In addition, the respective event elements may includepresentation time information and event identifiers of the events. Theevent identifiers may identify event instances. The presentation timeinformation may indicate start times of the events, and the start timesmay be indicated based on a time of the period. For example, a starttime of the period may be set to an offset, and a start time of anaction may be indicated using a difference from the start time of theperiod. This action may be referred to as an event according to context.

In a method of providing the broadcast service by the transmitting sideaccording to another embodiment of the present invention, the servicesignaling information may further include an EMT, and the EMT mayinclude event stream elements. Each of the event stream elements mayinclude event elements. These event elements may include informationabout events that signal actions to be performed by an application.Similarly, each of the event elements may include presentation timeinformation and an event identifier of the event.

In a method of providing the broadcast service by the transmitting sideaccording to another embodiment of the present invention, the EMT mayfurther include a period identifier and an MPD identifier of an MPD.Here, the MPD identifier may identify an MPD related to the EMT. Inother words, the MPD identifier may identify an MPD related to thecorresponding event. The period identifier may identify a period elementthat describes reproduction-related information of a certain interval ofreal-time content. This period element may identify a period related tothe corresponding event. Presentation time information may indicate astart time of an action based on an interval in a media presentationdescribed by the period element with respect to the period elementidentified by the MPD identifier and the period identifier. This actionmay be referred to as an event according to context.

A description will be given of a method of providing a broadcast serviceby a receiving side according to an embodiment of the present invention.This method is not illustrated in any figure.

The method of providing the broadcast service by the receiving sideaccording to the present embodiment may include receiving a broadcastsignal by a first module of the receiving side, physically processingthe broadcast signal to output link layer packets by a second module ofthe receiving side, link-processing the link layer packets to outputtransmission packets by a third module of the receiving side, acquiringan SLT and accessing an SLS by a fourth module of the receiving side,and/or acquiring a streaming component and/or an enhancement componentdelivered through a broadcast network using the SLS by a fifth module ofthe receiving side. Here, physical processing, link processing, etc. maycorrespond to reverse operations of those of the transmitting side.Here, service data may include a streaming component which includes dataabout real-time content of the broadcast service and/or enhancement datawhich includes data about application-based enhancement of real-timecontent. Service signaling information may include an AST which signalsapplications providing the application-based enhancement.

Methods of providing the broadcast service by the receiving sideaccording to embodiments of the present invention may correspond to themethods of providing the broadcast service by the transmitting sideaccording to the embodiments of the present invention described above.The methods of providing the broadcast service by the receiving side maybe performed by hardware modules corresponding to the modules used inthe methods of providing the broadcast service by the transmitting side(for example, the first, second, third, fourth, and fifth modules of thetransmitting side, etc.). The methods of providing the broadcast serviceby the receiving side may have embodiments corresponding to theembodiments of the methods of providing the broadcast service by thetransmitting side described above.

According to a given embodiment, the above-described steps may beomitted or replaced by other steps in which the same/similar operationsare performed.

FIG. 46 illustrates an apparatus for providing the broadcast service bythe transmitting side according to an embodiment of the presentinvention.

The apparatus for providing the broadcast service by the transmittingside according to the present embodiment may include the first second,third, fourth, and/or fifth modules of the transmitting side describedabove. The respective blocks and modules have been described above.

The apparatus for providing the broadcast service by the transmittingside according to the present embodiment and the internal modules/blocksmay perform the embodiments of the methods of providing the broadcastservice by the transmitting side of the present invention describedabove.

A description will be given of an apparatus for providing the broadcastservice by the receiving side according to an embodiment of the presentinvention. This apparatus is not illustrated in any figure.

The apparatus for providing the broadcast service by the receiving sideaccording to the present embodiment may include the first second, third,fourth, and/or fifth modules of the receiving side described above. Therespective blocks and modules have been described above.

The apparatus for providing the broadcast service by the receiving sideaccording to the present embodiment and the internal modules/blocks mayperform the embodiments of the methods of providing the broadcastservice by the receiving side of the present invention described above.

The internal modules/blocks of the apparatuses described above maycorrespond to processors for executing continuous processes stored in amemory, and may correspond to hardware elements located inside/outsidethe apparatuses according to a given embodiment.

According to a given embodiment, the above-described modules may beomitted or replaced by other modules for performing the same/similaroperations.

FIG. 47 illustrates an AST transmitted through a broadcast networkaccording to an embodiment of the present invention.

When the AST is transmitted through the broadcast network, an AST for anapplication enhancement may be transmitted through a service signalingchannel of the broadcast service to which the application enhancement isrelated. Here, the service signaling channel of the service may refer toa path through which the above-described SLS is delivered.

A broadcast signal (broadcast stream) having a certain frequency mayinclude service data and/or signaling data for the service. For example,the broadcast signal may be identified by the certain frequency.

The broadcast signal may include a first ROUTE session(sIP#A/dIP#A/dPort#A). The service data for the service may betransmitted through the first ROUTE session.

The service data may include a video component and/or an audio componentfor the service. The video component may include at least one videosegment having video data. The audio component may include at least oneaudio segment having audio data. The video component may be transmittedthrough a certain transmission session of the first ROUTE session. Theaudio component may be transmitted through another transmission sessionof the first ROUTE session.

The signaling data may include low level signaling data and/or servicelayer signaling data. For example, the low level signaling data mayinclude an FIT and/or an SLT. The low level signaling data may beincluded in an IP/UDP packet and transmitted. The service layersignaling data may be referred to as an SLS. The service layer signalingdata may include a USBD, an MPD, an S-TSID, and/or an AST. The USBD, theMPD, the S-TSID, and/or the AST may be transmitted through a certaintransmission session. For example, the SLS may be transmitted through acertain LCT transmission session included in the first ROUTE session(sIP#A/dIP#A/dPort#A). Specifically, the SLS may be transmitted througha first transmission session (tsi-sls) specified by tsi=0.

The first ROUTE session (sIP#A/dIP#A/dPort#A) may be identified by acombination of a source IP Address (sIP#A), a destination IP Address(dIP#A), and a destination port number (dPort#A). In addition, the firstROUTE session may be transmitted through at least one PLP. For example,the first ROUTE session may be transmitted through a first PLP (PLP #A).Further, the first ROUTE session may include the first transmissionsession (tsi-sls), a second transmission session (tsi-app), and/or athird transmission session (not illustrated).

The first transmission session (tsi-sls) may include at least oneservice layer signaling information. For example, the service layersignaling information may include at least one of the USBD, the MPD, theS-TSID, and/or the AST described above.

The second transmission session (tsi-app) may include at least oneapplication. For example, the application may refer to a set ofdocuments (HTML, CSS, JavaScript, etc.) included in anenhancement/interactive service.

The third transmission session may include a video component. Forexample, the video component may include at least one video segment. Atransmission object identifier for the video segment may have a certainvalue.

Hereinafter, the SLT (or FIT) will be described.

The SLT enables the receiver to create a basic service list andbootstrap discovery of an SLS for each service. The SLT may betransmitted through UDP/IP. The SLT may include bootstrappinginformation for acquiring basic information and service layer signalinginformation related to the service.

For example, the SLT may include a Broadcast_Stream_id attribute and afirst service element (Service #A).

The Broadcast_Stream_id attribute is an identifier of a whole broadcaststream. A value of a Broadcast_Stream_id field may be unique at aregional level.

The first service element (Service #A) may include at least one of aserviceId attribute and/or a signaling broadcast element.

The serviceId attribute may be an integer for uniquely identifying thecorresponding service in a range of a broadcast region.

The signaling_broadcast element may include information for signalinginformation for the service transmitted through the broadcast network.The signaling_broadcast element enables the receiver to bootstrapdiscovery of an SLS for each service.

The signaling_broadcast element may include at least one of a source IPAddress, a destination IP Address, a destination port number, a PLPID,and a transmission session identifier (TSI) related to an SLS for eachservice.

For example, the source IP Address, the destination IP Address, and/orthe destination port number may indicate the first ROUTE session(sIP#A/dIP#A/dPort#A). In addition, the PLPID may indicate the first PLP(PLP #A). Further, the TSI may indicate the first transmission session(tsi-sls).

Hereinafter, the SLS will be described.

The SLS may be transmitted through the broadcast network. The SLS may betransmitted through a certain LCT transmission session included in thefirst ROUTE session (sIP#A/dIP#A/dPort#A). Specifically, the SLS may betransmitted through the first transmission session (tsi-sls) specifiedby tsi=0. The SLS may include at least one of a USBD, an MPD, an S-TSID,and/or an AST.

The USBD may describe service layer attributes. In addition, the USBDmay include reference information (or a URI) referencing the MPD and/orthe S-TSID. Details of the USBD (C620210) may include whole contentabout the USBD described above.

The MPD may include resource identifiers for separate media componentsof a linear/streaming service. For example, the MPD may include a DASHMPD for all components transmitted through a mobile broadcast network, ageneral broadcast network, and/or an Internet protocol network. The DASHMPD may include a formalized description of DASH Media Presentation. TheDASH MPD may include resource identifiers for separate media componentsof the linear/streaming service. In addition, the DASH MPD may includecontext of resources identified in the media presentation. For example,the resource identifiers may correspond to information for identifyingrepresentation related to a component for the service. For example, theresource identifiers may have a form of a segment URL.

The S-TSID is a type of SLS XML fragment that provides all sessiondescription information for at least one transmission session fortransmitting at least one content component of the service.

The S-TSID may include a first ROUTE session element (RS) that providesinformation about a ROUTE session for a service and/or a componentincluded in the service. The first ROUTE session element (RS) mayinclude transmission path information for the first ROUTE session. Inaddition, the first ROUTE session element (RS) may include informationabout a transmission session (or a layered coding transport session)included in the ROUTE session. For example, the first ROUTE sessionelement (RS) may include a second transmission session element (LS)including information about the second transmission session. The secondtransmission session element (LS) may include transmission pathinformation for the second transmission session.

Specifically, the second transmission session element (LS) may include atsi attribute for identifying a transmission session in which a contentcomponent for the service is transmitted and a SrcFlow element thatdescribes a source flow included in the ROUTE session. The SrcFlowelement may include an nrt attribute that indicates whether the SrcFlowelement transmits NRT service data. Alternatively, the SrcFlow elementmay include an rt attribute that indicates whether the SrcFlow elementtransmits streaming media data. In other words, the nrt attribute mayperform the same function as that of the rt attribute. Further, the nrtattribute and the rt attribute may be replaced by each other. Forexample, when the tsi attribute corresponds to “tsi-app”, thecorresponding transmission session element may include information forthe second transmission session. In addition, when the nrt attributecorresponds to “true”, the SrcFlow element may transmit NRT servicedata.

The AST may include signaling information for an application. Details ofthe AST may include all of the above-described content.

The AST may include a ContentLinkage attribute. The ContentLinkageattribute may indicate an application that uses a corresponding contentitem. Signaling for a certain application may be performed by a value ofthis attribute and information about events (EventStream element, emsgbox, etc.) to be described below.

For example, the ContentLinkage attribute may provide an applicationidentifier for identifying an application which is transmitted throughthe second transmission session. Alternatively, the ContentLinkageattribute may provide a transmission session identifier for identifyingthe second transmission session (or LCT session).

A broadcast receiver may acquire a service based on signaling data.Specifically, the broadcast receiver may acquire low level signalingdata, and acquire service layer signaling data based on the low levelsignaling data.

In addition, the broadcast receiver may acquire an attribute of theservice using the service layer signaling data (USBD). Further, thebroadcast receiver may refer to and/or acquire an MPD and/or an S-TSIDusing the USBD.

In addition, the broadcast receiver may acquire information about atleast one component (or representation) for the service using theservice layer signaling data (USBD and/or MPD). For example, thebroadcast receiver may acquire information about a video component.

In addition, the broadcast receiver may acquire transmission pathinformation of at least one component using the service layer signalingdata (S-TSID). Further, the broadcast receiver may acquire transmissionpath information of another component for the at least one componentusing the service layer signaling data (S-TSID). For example, the othercomponent for the at least one component may include the application.

In addition, the broadcast receiver may acquire service data for theservice based on the service layer signaling data (transmission pathinformation). For example, the broadcast receiver may receive theapplication in non-real time through the second transmission session(tsi-app).

In addition, the broadcast receiver may acquire information foridentifying the application based on the service layer signaling data(AST).

The broadcast receiver may operate the application at predeterminedtiming while reproducing the video component.

FIG. 48 illustrates an AST transmitted through a broadband networkaccording to an embodiment of the present invention.

When the AST is transmitted through the broadband network, the AST maybe acquired through a query. This query may be generated usinginformation about a base URL in an SLT. This base URL may correspond toURL information for acquiring the AST. Here, the SLT may correspond toan SLT including bootstrap information for a broadcast service relatedto the AST.

A broadcast signal (broadcast stream) having a certain frequency mayinclude service data and/or signaling data for the service. Thebroadcast signal may include a first ROUTE session(sIP#A/dIP#A/dPort#A). The first ROUTE session may be transmittedthrough a first PLP (PLP #A). In addition, the first ROUTE session mayinclude a first transmission session (not illustrated), a secondtransmission session (tsi-app), and/or a third transmission session (notillustrated). The first transmission session may include at least oneservice layer signaling information. The second transmission session(tsi-app) may include at least one application. The third transmissionsession may include a video component. Content about the first ROUTEsession (sIP#A/dIP#A/dPort#A), the first PLP (PLP #A), the firsttransmission session, the second transmission session (tsi-app), and/orthe third transmission session may include all of the above-describedcontent about the first ROUTE session (sIP#A/dIP#A/dPort#A), the firstPLP (PLP #A), the first transmission session, the second transmissionsession (tsi-app), and/or the third transmission session.

Hereinafter, the SLT (or FIT) will be described.

Content about the SLT according to an embodiment of the presentinvention may include all of the above-described content of the SLT.Hereinafter, a description will be given focusing on differences.

For example, the SLT may include a Broadcast_Stream_id attribute and afirst service element (Service #A). The first service element (Service#A) may include at least one of a serviceId attribute and/or asignaling_broadband element.

The serviceId attribute may correspond to an integer for uniquelyidentifying the corresponding service in a range of a broadcast region.

The signaling broadband element may include path information (or URL)for accessing Internet signaling information (for example, SLS) for theservice. The signaling broadband element enables the receiver tobootstrap discovery of an SLS for each service. In this case, the SLSmay be transmitted through the broadband network.

The signaling_broadband element may include broadbandServerURL_AST whichincludes path information (or URL) for accessing the AST for theservice. In this case, the AST may be transmitted through the broadbandnetwork.

Hereinafter, the SLS will be described.

The SLS may include at least one of a USBD, an MPD, an S-TSID, and/or anAST. Content related to the SLS may include all of the above-describedcontent about the SLS. However, one difference is that the SLS may betransmitted through the broadband network.

The broadcast receiver according to the present embodiment may receive,through a broadcast network, a broadcast signal including at least oneof service data and signaling data (for example, low level signalingdata or SLT) for the service.

The broadcast receiver according to the present embodiment may acquirethe service based on the signaling data. Specifically, the broadcastreceiver may acquire the low level signaling data, and acquire servicelayer signaling data based on the low level signaling data. The servicelayer signaling data may be transmitted through the broadband network.

In addition, the broadcast receiver may acquire an attribute of theservice using the service layer signaling data (USBD). Further, thebroadcast receiver may refer to and/or acquire the MPD and/or the S-TSIDusing the USBD.

In addition, the broadcast receiver may acquire information about atleast one component (or representation) for the service using theservice layer signaling data (USBD and/or MPD). For example, thebroadcast receiver may acquire information about a video component.

In addition, the broadcast receiver may acquire transmission pathinformation of at least one component using the service layer signalingdata (S-TSID). Further, the broadcast receiver may acquire transmissionpath information of another component for the at least one componentusing the service layer signaling data (S-TSID). For example, the othercomponent for the at least one component may include the application.

In addition, the broadcast receiver may acquire service data for theservice based on the service layer signaling data (transmission pathinformation). For example, the broadcast receiver may receive theapplication in non-real time through the second transmission session(tsi-app).

In addition, the broadcast receiver may acquire information foridentifying the application based on the service layer signaling data(AST).

The broadcast receiver may operate the application at predeterminedtiming while reproducing the video component.

FIG. 49 illustrates an event transmitted in the form of an EventStreamelement through a broadcast network according to an embodiment of thepresent invention.

The event may be transmitted in the form of the EventStream elementwhich appears in a Period element of an MPD. Content about theEventStream element which is transmitted through the broadcast networkmay include all of the above-described content about the EventStreamelement.

A broadcast signal (broadcast stream) having a certain frequency mayinclude service data and/or signaling data for the service. Thebroadcast signal may include a first ROUTE session(sIP#A/dIP#A/dPort#A). The first ROUTE session may be transmittedthrough a first PLP (PLP #A). In addition, the first ROUTE session mayinclude a first transmission session (tsi-sls), a second transmissionsession (tsi-app), and/or a third transmission session (notillustrated). The first transmission session (tsi-sls) may include atleast one service layer signaling information. For example, the servicelayer signaling information may include at least one of the USBD, theMPD, the S-TSID, and/or the AST described above. The second transmissionsession (tsi-app) may include at least one application. The thirdtransmission session may include a video component. Content about thefirst ROUTE session (sIP#A/dIP#A/dPort#A), the first PLP (PLP #A), thefirst transmission session, the second transmission session (tsi-app),and/or the third transmission session may include all of theabove-described content about the first ROUTE session(sIP#A/dIP#A/dPort#A), the first PLP (PLP #A), the first transmissionsession, the second transmission session (tsi-app), and/or the thirdtransmission session.

Hereinafter, an SLT will be described.

The SLT enables the receiver to create a basic service list andbootstrap discovery of an SLS for each service. For example, the SLT mayinclude path information for the first ROUTE session(sIP#A/dIP#A/dPort#A). In addition, the SLT may include path informationfor the first transmission session (tsi-sls). Content about the SLTaccording to the present embodiment may include all of theabove-described content about the SLT.

Hereinafter, the SLS will be described.

The SLS may include at least one of a USBD, an MPD, an S-TSID, and/or anAST. Content related to the SLS may include all of the above-describedcontent about the SLS. Hereinafter, the MPD will be described in furtherdetail.

The MPD corresponds to service signaling information for a certainservice, and may provide signaling information at a time interval of theservice referred to as a period. Signaling information related to theperiod is included in an MPD Period element, and this Period element mayinclude an EventStream element. The EventStream element may providesignaling (event) necessary for operations of applications during theperiod of the service.

The EventStream element may include a schemeldUri attribute, a valueattribute, a timescale attribute, and/or at least one Event sub-element.Each Event sub-element may include a presentationTime attribute, aduration attribute and/or an id attribute. Details of the EventStreamelement may include all of the above-described content about theEventStream element.

For example, the schemeldUri attribute may have a value of“urn:uuid:XYZY”. In addition, the value attribute may have a value of“call”. Further, the timescale attribute may have a value of “1000”.

In addition, with regard to a first event, the presentationTimeattribute may have a value of “0”, the duration attribute may have avalue of “10000”, and/or the id attribute may have a value of “0”.Further, a data element/attribute may correspond to “+1 800 10101010”.

With regard to a second event, the presentationTime attribute may have avalue of “20000”, the duration attribute may have a value of “10000”,and/or the id attribute may have a value of “1”. Further, a dataelement/attribute may correspond to “+1 800 10101011”.

With regard to a third event, the presentationTime attribute may have avalue of “40000”, the duration attribute may have a value of “10000”,and/or the id attribute may have a value of “2”. Further, a dataelement/attribute may correspond to “+1 800 10101012”.

With regard to a fourth event, the presentationTime attribute may have avalue of “60000”, the duration attribute may have a value of “10000”,and/or the id attribute may have a value of “3”. Further, a dataelement/attribute may correspond to “+1 800 10101013”.

The broadcast receiver according to the present embodiment may receive abroadcast signal including at least one of service data and signalingdata (for example, low level signaling data or service layer signalingdata) for a service through a broadcast network.

The broadcast receiver according to the present embodiment may acquirethe service based on the signaling data. Specifically, the broadcastreceiver may acquire the low level signaling data, and acquire theservice layer signaling data based on the low level signaling data.

In addition, the broadcast receiver may acquire an attribute of theservice using the service layer signaling data (USBD). Further, thebroadcast receiver may refer to and/or acquire an MPD and/or an S-TSIDusing the USBD.

In addition, the broadcast receiver may acquire information about atleast one component (or representation) for the service using theservice layer signaling data (USBD and/or MPD). For example, thebroadcast receiver may acquire information about a video component.

In addition, the broadcast receiver may acquire transmission pathinformation of at least one component using the service layer signalingdata (S-TSID). Further, the broadcast receiver may acquire transmissionpath information of another component for the at least one componentusing the service layer signaling data (S-TSID). For example, the othercomponent for the at least one component may include the application.

In addition, the broadcast receiver may acquire service data for theservice based on the service layer signaling data (transmission pathinformation). For example, the broadcast receiver may receive theapplication in non-real time through the second transmission session(tsi-app).

In addition, the broadcast receiver may acquire information foridentifying the application based on the service layer signaling data(AST).

In addition, the broadcast receiver may operate the application based onthe event. For example, the event may be transmitted in the form of theEventStream element which appears in the Period element. The broadcastreceiver may operate the application at predetermined timing whilereproducing the video component.

FIG. 50 illustrates an event transmitted in the form of an emsg boxthrough a broadcast network according to an embodiment of the presentinvention.

The event may be transmitted in the form of the emsg box which appearsin segments of Representation (or Representation segments). Contentabout the emsg box transmitted through the broadcast network may includeall of the above-described content about the emsg box.

A broadcast signal (broadcast stream) having a certain frequency mayinclude service data and/or signaling data for a service. The broadcastsignal may include a first ROUTE session (sIP#A/dIP#A/dPort#A). Thefirst ROUTE session may be transmitted through a first PLP (PLP #A). Inaddition, the first ROUTE session may include a first transmissionsession (tsi-sls), a second transmission session (tsi-app), and/or athird transmission session (tsi-v). The first transmission session(tsi-sls) may include at least one service layer signaling information.For example, the service layer signaling information may include atleast one of the USBD, the MPD, the S-TSID, and/or the AST describedabove. The second transmission session (tsi-app) may include at leastone application. The third transmission session may include a videocomponent. The video component may include at least one video segmentwhich includes video data. The at least one video segment may includethe emsg box.

Content about the first ROUTE session (sIP#A/dIP#A/dPort#A), the firstPLP (PLP #A), the first transmission session, the second transmissionsession (tsi-app), and/or the third transmission session (tsi-v) mayinclude all of the above-described content about the first ROUTE session(sIP#A/dIP#A/dPort#A), the first PLP (PLP #A), the first transmissionsession, the second transmission session (tsi-app), and/or the thirdtransmission session (tsi-v).

Hereinafter, the emsg box included in the segments will be described.

The emsg box may provide signaling information for generic eventsrelated to a media presentation time. The emsg box may include at leastone of a schemeldUri field, a value field, a timescale field, apresentationTimeDelta field, an eventDuration field, an id field, and/ora messageData field. Content about the emsg box may include all of theabove-described content of the emsg box.

Hereinafter, an SLT will be described.

The SLT enables the receiver to create a basic service list andbootstrap discovery of an SLS for each service. For example, the SLT mayinclude path information for the first ROUTE session(sIP#A/dIP#A/dPort#A). In addition, the SLT may include path informationfor the first transmission session (tsi-sls). Content about the SLTaccording to the present embodiment may include all of theabove-described content about the SLT.

Hereinafter, the SLS will be described.

The SLS may include at least one of a USBD, an MPD, an S-TSID, and/or anAST. Content related to the SLS may include all of the above-describedcontent about the SLS. Hereinafter, the S-TSID and/or the MPD will bedescribed in further detail.

The S-TSID may include a first ROUTE session element (RS) that providesinformation about a ROUTE session for a service and/or a componentincluded in the service. The first ROUTE session element (RS) mayinclude transmission path information for the first ROUTE session. Inaddition, the first ROUTE session element (RS) may include informationabout a transmission session (or a layered coding transport session)included in the ROUTE session. For example, the first ROUTE sessionelement (RS) may include a second transmission session element (LS)including information about the second transmission session. The secondtransmission session element (LS) may include transmission pathinformation for the second transmission session. In addition, the firstROUTE session element (RS) may include a third transmission sessionelement (LS) including information about the third transmission session.The third transmission session element (LS) may include transmissionpath information for the third transmission session.

Specifically, each of the second transmission session element (LS)and/or the third transmission session element (LS) may include a tsiattribute for identifying a transmission session in which a contentcomponent for the service is transmitted and a SrcFlow element thatdescribes a source flow included in the ROUTE session.

The SrcFlow element may include an nrt attribute that indicates whetherthe SrcFlow element transmits NRT service data. Alternatively, theSrcFlow element may include an rt attribute that indicates whether theSrcFlow element transmits streaming media data. In other words, the nrtattribute may perform the same function as that of the rt attribute.Further, the nrt attribute and the rt attribute may be replaced by eachother.

The SrcFlow element may further include an appID attribute whichincludes additional information mapped to a service (or an applicationservice) transmitted through a transmission session. The appID attributemay be referred to as a ContentInfo element. The ContentInfo element mayinclude additional information mapped to the service (or the applicationservice) transmitted through the transmission session. For example, theContentInfo element may include a representation identifier (ID) of DASHcontent and/or adaptation set parameters of DASH media representation inorder to select an LCT transmission session for rendering. Therepresentation ID is an ID related to a component for the service, andmay be referred to as an id attribute. Therefore, the appID attribute inthe SrcFlow element may be matched with an id attribute in aRepresentation element of the MPD.

With regard to the second transmission session element (LS), when thetsi attribute corresponds to “tsi-app”, the transmission session elementmay include information for the second transmission session. Inaddition, when the nrt attribute corresponds to “true”, the SrcFlowelement may transmit NRT service data. In other words, the applicationmay be transmitted in non-real time through the second transmissionsession (tsi-app).

With regard to the third transmission session element (LS), when the tsiattribute corresponds to “tsi-app”, the transmission session element mayinclude information for the third transmission session. In addition,when the nrt attribute corresponds to “false”, the SrcFlow element maytransmit real-time service data. Further, when the appID attributecorresponds to “rep_vl”, a representation ID of the video component maycorrespond to “rep_vl”. In other words, at least one video segment ofthe video component identified by “rep_vl” may be transmitted in realtime through the third transmission session (tsi-v).

The MPD may include resource identifiers for separate media componentsof a linear/streaming service. The MPD may include the Period element.The Period element may include an AdaptationSet element which includesinformation about the video component. The AdaptationSet element mayinclude at least one Representation element. The Representation elementmay include information about a representation related to the component.

The Representation element may include an id attribute for identifyingthe representation. For example, the id attribute may have a value of“rep_vl”. In other words, the id attribute may indicate the videocomponent transmitted through the third transmission session (tsi-v).

In addition, the Representation element may further include anInbandEventStream element that specifies the presence of an in-bandevent stream in the related representation. The InbandEventStreamelement of the Representation element of the MPD may signal whether anevent is present the emsg box in the segments.

The InbandEventStream element may include a schemeIdURI attribute and/ora value attribute. These two attributes may indicate a type of the eventin the emsg box. According to a given embodiment, these two attributesmay be used to identify the event. The schemeIdURI attribute and/or thevalue attribute included in the InbandEventStream element may be matchedwith a schemeIdURI attribute and/or a value attribute in the emsg box.For example, the schemeIdURI attribute may have a value of “event_URI#1”, and the value attribute may have a value of“abc”.

The broadcast receiver according to the present embodiment may receive abroadcast signal including at least one of service data and signalingdata (for example, low level signaling data or service layer signalingdata) for a service through a broadcast network.

The broadcast receiver according to the present embodiment may acquirethe service based on the signaling data. Specifically, the broadcastreceiver may acquire the low level signaling data, and acquire theservice layer signaling data based on the low level signaling data.

In addition, the broadcast receiver may acquire an attribute of theservice using the service layer signaling data (USBD). Further, thebroadcast receiver may refer to and/or acquire an MPD and/or an S-TSIDusing the USBD.

In addition, the broadcast receiver may acquire information about atleast one component (or representation) for the service using theservice layer signaling data (USBD and/or MPD). For example, thebroadcast receiver may acquire information about a video component. Inthis instance, the Representation element of the MPD may include anInbandEventStream element that specifies the presence of the emsg box(or in-band event stream) in the video component.

In addition, the broadcast receiver may acquire transmission pathinformation of at least one component using the service layer signalingdata (S-TSID). Further, the broadcast receiver may acquire transmissionpath information of another component for the at least one componentusing the service layer signaling data (S-TSID). For example, the othercomponent for the at least one component may include the application.

In addition, the broadcast receiver may acquire service data for theservice based on the service layer signaling data (transmission pathinformation). For example, the broadcast receiver may receive theapplication in non-real time through the second transmission session(tsi-app). Further, the broadcast receiver may receive at least onevideo segment of the video component identified by “rep_vl” through thethird transmission session (tsi-v) in real time. The at least one videosegment may include the emsg box.

In addition, the broadcast receiver may acquire information foridentifying the application based on the service layer signaling data(AST).

In addition, the broadcast receiver may operate the application based onthe event. For example, the event may be included in the segments in theform of the emsg box. The broadcast receiver may operate the applicationat predetermined timing while reproducing the video component.

FIG. 51 illustrates an event transmitted in the form of an EventStreamelement through a broadband network according to an embodiment of thepresent invention.

The event may be transmitted in the form of the EventStream elementwhich is included in an EST transmitted through the broadband network.When the EST is transmitted through the broadband network, the EST maybe acquired through a query. This query may be generated using URLinformation in an ALT. This URL information may be URL information foracquiring the EST. Content about the EventStream element transmittedthrough the broadband network may include all of the above-describedcontent about the EventStream element.

A broadcast signal (broadcast stream) having a certain frequency mayinclude service data and/or signaling data for a service. The broadcastsignal may include a first ROUTE session (sIP#A/dIP#A/dPort#A). Thefirst ROUTE session may be transmitted through a first PLP (PLP #A). Inaddition, the first ROUTE session may include a first transmissionsession (tsi-sls), a second transmission session (tsi-app), and/or athird transmission session (not illustrated). The first transmissionsession (tsi-sls) may include at least one service layer signalinginformation. For example, the service layer signaling information mayinclude at least one of the USBD, the MPD (not illustrated), the S-TSID,and/or the AST described above. The second transmission session(tsi-app) may include at least one application. The third transmissionsession may include a video component. According to a given embodiment,the MPD may be omitted. Content about the first ROUTE session(sIP#A/dIP#A/dPort#A), the first PLP (PLP #A), the first transmissionsession, the second transmission session (tsi-app), and/or the thirdtransmission session according to the present embodiment may include allof the above-described content about the first ROUTE session(sIP#A/dIP#A/dPort#A), the first PLP (PLP #A), the first transmissionsession, the second transmission session (tsi-app), and/or the thirdtransmission session.

Hereinafter, an SLT will be described.

The SLT may include path information for the first ROUTE session(sIP#A/dIP#A/dPort#A). In addition, the SLT may include path informationfor the first transmission session (tsi-sls). Content about the SLTaccording to the present embodiment may include all of theabove-described content of the SLT.

Hereinafter, an SLS will be described.

The SLS may include at least one of a USBD, an MPD, an S-TSID, and/or anAST. Content about the SLS may include all of the above-describedcontent about the SLS. Hereinafter, the AST will be described in furtherdetail.

The AST may include a ContentLinkage attribute. The ContentLinkageattribute may indicate an application that uses a corresponding contentitem. Signaling for a certain application may be performed by a value ofthis attribute and information about events (EventStream element, emsgbox, etc.) to be described below.

For example, the ContentLinkage attribute may provide an applicationidentifier for identifying an application which is transmitted throughthe second transmission session. Alternatively, the ContentLinkageattribute may provide a transmission session identifier for identifyingthe second transmission session (or LCT session).

The AST may further include a BroadbandStaticEventURL attribute. TheBroadbandStaticEventURL attribute may include path information (or aURL) for accessing the EST for the service. In this case, the EST may betransmitted through the broadband network. The EST may include anEventStream element. The EventStream element may provide signaling(event) necessary for operations of applications.

The EventStream element may include a schemeldUri attribute, a valueattribute, a timescale attribute, and/or at least one Event sub-element.Each Event sub-element may include a presentationTime attribute, aduration attribute and/or an id attribute. Details of the EventStreamelement may include all of the above-described content about theEventStream element.

For example, the schemeldUri attribute may have a value of“urn:uuid:XYZY”. In addition, the value attribute may have a value of“call”. Further, the timescale attribute may have a value of “1000”.

In addition, with regard to a first event, the presentationTimeattribute may have a value of “0”, the duration attribute may have avalue of “10000”, and/or the id attribute may have a value of “0”.Further, a data element/attribute may correspond to “+1 800 10101010”.

With regard to a second event, the presentationTime attribute may have avalue of “20000”, the duration attribute may have a value of “10000”,and/or the id attribute may have a value of “1”. Further, a dataelement/attribute may correspond to “+1 800 10101011”.

With regard to a third event, the presentationTime attribute may have avalue of “40000”, the duration attribute may have a value of “10000”,and/or the id attribute may have a value of “2”. Further, a dataelement/attribute may correspond to “+1 800 10101012”.

With regard to a fourth event, the presentationTime attribute may have avalue of “60000”, the duration attribute may have a value of “10000”,and/or the id attribute may have a value of “3”. Further, a dataelement/attribute may correspond to “+1 800 10101013”.

The broadcast receiver according to the present embodiment may receive abroadcast signal including at least one of service data and signalingdata (for example, low level signaling data or service layer signalingdata) for a service through a broadcast network.

The broadcast receiver according to the present embodiment may acquirethe service based on the signaling data. Specifically, the broadcastreceiver may acquire the low level signaling data, and acquire theservice layer signaling data based on the low level signaling data.

In addition, the broadcast receiver may acquire an attribute of theservice using the service layer signaling data (USBD). Further, thebroadcast receiver may refer to and/or acquire an MPD and/or an S-TSIDusing the USBD.

In addition, the broadcast receiver may acquire information about atleast one component (or representation) for the service using theservice layer signaling data (USBD and/or MPD). For example, thebroadcast receiver may acquire information about a video component.

In addition, the broadcast receiver may acquire transmission pathinformation of at least one component using the service layer signalingdata (S-TSID). Further, the broadcast receiver may acquire transmissionpath information of another component for the at least one componentusing the service layer signaling data (S-TSID). For example, the othercomponent for the at least one component may include the application.

In addition, the broadcast receiver may acquire service data for theservice based on the service layer signaling data (transmission pathinformation). For example, the broadcast receiver may receive theapplication in non-real time through the second transmission session(tsi-app).

In addition, the broadcast receiver may acquire information foridentifying the application based on the service layer signaling data(AST). Further, the broadcast receiver may acquire the EST through thebroadband network based on the service layer signaling data (AST).

In addition, the broadcast receiver may operate the application based onthe event. For example, the event may be transmitted in the form of theEventStream element which is included in the EST transmitted through thebroadband network.

The broadcast receiver may operate the application at predeterminedtiming while reproducing the video component.

FIG. 52 illustrates an event transmitted in the form of an emsg boxthrough a broadband network according to an embodiment of the presentinvention.

The event may be transmitted in the form of the emsg box transmittedthrough the broadband network. In this case, the event may be deliveredthrough a live event server. Polling may be periodically performed usingthe live event server. When an event to be transmitted in thecorresponding period is present, the event server may deliver the eventto a receiver. Content about the emsg box transmitted through thebroadband network may include all of the above-described content aboutthe emsg box.

A broadcast signal (broadcast stream) having a certain frequency mayinclude service data and/or signaling data for a service. The broadcastsignal may include a first ROUTE session (sIP#A/dIP#A/dPort#A). Thefirst ROUTE session may be transmitted through a first PLP (PLP #A). Inaddition, the first ROUTE session may include a first transmissionsession (tsi-sls), a second transmission session (tsi-app), and/or athird transmission session (not illustrated). The first transmissionsession (tsi-sls) may include at least one service layer signalinginformation. For example, the service layer signaling information mayinclude at least one of the USBD, the MPD (not illustrated), the S-TSID,and/or the AST described above. The second transmission session(tsi-app) may include at least one application. The third transmissionsession may include a video component. According to a given embodiment,the MPD may be omitted. Content about the first ROUTE session(slP#A/dlP#A/dPort#A), the first PLP (PLP #A), the first transmissionsession, the second transmission session (tsi-app), and/or the thirdtransmission session according to the present embodiment may include allof the above-described content about the first ROUTE session(slP#A/dlP#A/dPort#A), the first PLP (PLP #A), the first transmissionsession, the second transmission session (tsi-app), and/or the thirdtransmission session.

Hereinafter, an SLT will be described.

The SLT may include path information for the first ROUTE session(slP#A/dlP#A/dPort#A). In addition, the SLT may include path informationfor the first transmission session (tsi-sls). Content about the SLTaccording to the present embodiment may include all of theabove-described content of the SLT.

Hereinafter, an SLS will be described.

The SLS may include at least one of a USBD, an MPD, an S-TSID, and/or anAST. Content about the SLS may include all of the above-describedcontent about the SLS. Hereinafter, the AST will be described in furtherdetail.

The AST may include a ContentLinkage attribute. The ContentLinkageattribute may indicate an application that uses a corresponding contentitem. Signaling for a certain application may be performed using a valueof this attribute and information about events (EventStream element,emsg box, etc.) to be described below.

For example, the ContentLinkage attribute may provide an applicationidentifier for identifying an application which is transmitted throughthe second transmission session. Alternatively, the ContentLinkageattribute may provide a transmission session identifier for identifyingthe second transmission session (or LCT session).

The AST may further include a BroadbandStaticEventURL attribute. TheBroadbandStaticEventURL attribute may include path information (or aURL) for accessing the emsg box for the service. In this case, the emsgbox may be transmitted through the broadband network. The emsg box mayprovide signaling (event) necessary for operations of applications.

The emsg box may provide signaling information for generic eventsrelated to a media presentation time. The emsg box may include at leastone of a schemeldUri field, a value field, a timescale field, apresentationTimeDelta field, an eventDuration field, an id field, and/ora messageData field. Content about the emsg box may include all of theabove-described content of the emsg box.

For example, the schemeldUri field may have a value of “urn:uuid:XYZY”.

The broadcast receiver according to the present embodiment may receive abroadcast signal including at least one of service data and signalingdata (for example, low level signaling data or service layer signalingdata) for a service through a broadcast network.

The broadcast receiver according to the present embodiment may acquirethe service based on the signaling data. Specifically, the broadcastreceiver may acquire the low level signaling data, and acquire theservice layer signaling data based on the low level signaling data.

In addition, the broadcast receiver may acquire an attribute of theservice using the service layer signaling data (USBD). Further, thebroadcast receiver may refer to and/or acquire an MPD and/or an S-TSIDusing the USBD.

In addition, the broadcast receiver may acquire information about atleast one component (or representation) for the service using theservice layer signaling data (USBD and/or MPD). For example, thebroadcast receiver may acquire information about a video component.

In addition, the broadcast receiver may acquire transmission pathinformation of at least one component using the service layer signalingdata (S-TSID). Further, the broadcast receiver may acquire transmissionpath information of another component for the at least one componentusing the service layer signaling data (S-TSID). For example, the othercomponent for the at least one component may include the application.

In addition, the broadcast receiver may acquire service data for theservice based on the service layer signaling data (transmission pathinformation). For example, the broadcast receiver may receive theapplication in non-real time through the second transmission session(tsi-app).

In addition, the broadcast receiver may acquire information foridentifying the application based on the service layer signaling data(AST). Further, the broadcast receiver may acquire the emsg box throughthe broadband network based on the service layer signaling data (AST).

In addition, the broadcast receiver may operate the application based onthe event. For example, the event may be transmitted in the form of theemsg box transmitted through the broadband network.

The broadcast receiver may operate the application at predeterminedtiming while reproducing the video component.

FIG. 53 illustrates an API and an event listener according to anembodiment of the present invention.

FIG. 53(a) illustrates the listener.

An event processor may correspond to code executed in response tooccurrence of an event. For example, the event processor may correspondto JavaScript code for execution when the event occurs. The eventprocessor may include the event listener (or listener). Unlike an eventhandler which can process only one event for one element, the eventlistener may process at least one event for one element.

The listener may include a general signature of a document object model(DOM) event listener. Here, a DOM refers to a model (system) thatsupports the event handler such that the event handler is connectable toall element nodes.

The listener according to the present embodiment may include an objectof a StreamEvent type as a parameter. For example, the listener may havea form such as listener (StreamEvent event).

The object of the StreamEvent type delivered to the listener has anextended form of an object of a general DOM event type.

The object of the StreamEvent type may include a name attribute, a dataattribute, a text attribute, a status attribute, and/or a timeattribute.

The name attribute may indicate a name of an event. The name attributeis a read-only attribute, and may correspond to a string type.

The data attribute may indicate data of an event encoded as ahexadecimal number. For example, the data attribute may have a value of“0A10B81033”. The data attribute is a read-only attribute, and maycorrespond to a string type.

The text attribute may indicate text data of an event. For example, whenthe data attribute includes text, the text attribute may have values inASCII code. In addition, the text attribute may correspond to a childelement of an Event element for activation of the event, and includedata identified by a data identifier (dataID) which is specified in atrigger or specified in an Event element of an EMT. The text attributeis a read-only attribute, and may correspond to a string type.

The status attribute may indicate a state of an event. When the event isactivated in response to a trigger, the status attribute may indicate“trigger”. When several types of errors occur, the status attribute mayindicate “error”. The status attribute is a read-only attribute, and maycorrespond to a DOMString type.

The time attribute may indicate a time at which an event occurs. Thetime attribute is a read-only attribute, and may have an integer type.

FIG. 53(b) illustrates the API for addition and/or deletion of the eventlistener (or listener).

A method of processing an event according to an embodiment of thepresent invention may include a scheme of connecting the event listenerto a method of an object. This method is a method of connecting theevent listener to the method of the object, and executing the method ofthe object when the event occurs thereafter.

AddStreamEventListener API and/or removeStreamEventListener APIaccording to an embodiment of the present invention may be used tosupport this method of processing the event.

AddStreamEventListener API may add the listener for the event (forexample, the event listener or a stream event listener).AddStreamEventListener API may add a listener for an event designated byan event identifier (for example, eventID) within a range of a currentlyexecuted html application to an AST. When the event is activated by atrigger, the listener is called. In addition, an object of aTriggerEvent type (or a StreamEvent type) may be delivered. Listenersmay be added only when a video/broadcast object is in a presentingand/or stopped state.

AddStreamEventListener API may include at least one of a targetURLparameter, an eventName parameter, and/or a Listener parameter. Forexample, addStreamEventListener API may have a form such asaddStreamEventListener(targetURL, eventName, listener).

The targetURL parameter may indicate a URL of a StreamEvent object thatdescribes an event. Alternatively, the targetURL parameter may be mappedto a schemeIdURI attribute of a DASH EventStream element.

The eventName parameter may indicate a name of an event to besubscribed. Alternatively, the eventName parameter may be mapped to avalue attribute of the DASH EventStream element.

The Listener parameter may indicate a listener for an event. TheListener parameter may correspond to a callback function. When the eventoccurs, the Listener parameter may be called as a parameter togetherwith a delivered StreamEvent object.

The targetURL parameter and the eventName parameter may correspond toevent identifiers for identifying an event. For example,addStreamEventListener API may include an event identifier (eventId)parameter and a listener parameter. For example, addStreamEventListenerAPI may have a form of addTriggerEventListener(String eventId,EventListener listener). The event identifier may correspond to anidentifier (for example, an EventID attribute or an id attribute) of anevent present in an event element in the EMT. In addition, the eventidentifier may correspond to an identifier (for example, an id field ofan emsg box) of an event dynamically updated by a trigger.

RemoveStreamEventListener API may delete a listener for an event.RemoveStreamEventListener API may delete a listener for an eventdesignated by an event identifier (for example, eventID).

RemoveStreamEventListener API may include at least one of a targetURLparameter, an eventName parameter, and/or a Listener parameter. Forexample, removeStreamEventListener API may have a form such asremoveStreamEventListener(targetURL, eventName, listener).

The targetURL parameter may indicate a URL of a StreamEvent object.Alternatively, the targetURL parameter may be mapped to a schemeIdURIattribute of a DASH EventStream element.

The eventName parameter may indicate a name of an event, subscription ofwhich needs to be deleted. Alternatively, the eventName parameter may bemapped to a value attribute of the DASH EventStream element.

The Listener parameter may indicate a listener for an event. TheListener parameter may correspond to a callback function. When the eventoccurs, the Listener parameter may be called out as a parameter togetherwith a delivered StreamEvent object.

The targetURL parameter and the eventName parameter may correspond toevent identifiers for identifying an event. For example,removeStreamEventListener API may include an event identifier (eventId)parameter and a listener parameter. For example,removeStreamEventListener API may have a form ofremoveTriggerEventListener(String eventId, EventListener listener). Theevent identifier may correspond to an identifier (for example, anEventID attribute or an id attribute) of an event present in an eventelement in the EMT. In addition, the event identifier may correspond toan identifier (for example, an id field of an emsg box) of an eventdynamically updated by a trigger.

The broadcast receiver according to the present embodiment may add alistener for an event based on addStreamEventListener API. In addition,the broadcast receiver may add a listener for an event based onremoveStreamEventListener API. AddStreamEventListener API and/orremoveStreamEventListener API may support synchronization of htmlapplication actions for broadcast programming.

FIG. 54 is a diagram illustrating a hierarchical signaling structureaccording to an embodiment of the present invention.

Prior to description of a hierarchical signaling structure of abroadcast system according to the present invention, terms used in thepresent invention may be defined as follows.

The 3GPP represents a 3^(rd) Generation Partnership Project.

The ALC represents Asynchronous Layered Coding. For details of a relatedprotocol, reference can be made to the document RFC 5775 such as layeredcoding transport (LCT).

The Broadband Stream may correspond to an RF channel. The RF channel maybe defined as a center carrier frequency of a specific bandwidth.

The DASH represents Dynamic Adaptive Streaming over HTTP. For the abovedetails, reference can be made to content of the document ISO/IEC23009-1.

The eMBMS represents an evolved Multimedia Broadcast/Multicast Service.The eMBMS may be technology for describing content of a cellular mobilebroadcast of a service through an LTE network.

The FIT represents a Fast Information Table. The FIT may generate abasic service list and include information for bootstrapping discoveryof a ROUTE session for transmitting an SLS and an LCT channel.

The LCT represents a Layered Coding Transport. The LCT may be buildingblock technology defined in the document RFC 5651 and provide support ofa stream transport protocol and a transport level for supportingreliable content transmission.

The LLS represents Link Layer Signaling. The LLS may correspond tosignaling information that is transmitted by a payload of a packet of asecond layer prior to a third layer (e.g., an IP layer).

The MMTP represents MPEG Multimedia Transport. For details of the MMTP,reference can be made to the document ISO/IEC 23008-1.

The MPD represents Media Presentation Description. The MPD may includeformulated details of DASH media presentation for providing a streamingservice. The MPD may be included in a fragment of SLS in order totransmit a streaming service.

The MPU represents a Media Processing Unit. For details of the MPU,reference can be made to the document ISO/IEC 23008-1.

The PLP represents a Physical Layer Pipe. The PLP may be a portion oftransmission capacity provided by a broadcast stream, for transmittingservice meta data such as service signaling and/or a content componentof an ATSC3.0 service and may correspond to a combination of data itemsassociated by a specific modulation and coding parameter.

The ROUTE represents Real-Time Object delivery Over UnidirectionalTransport. The ROUTE may define technology for allowing real-timestreaming for service providing via file-based transmission.

The SLS represents Service Layer Signaling. The SLS may includeinformation required to discover and acquire an ATSC3.0 service andcontent components thereof. The SLS data may be transmitted by a thirdlayer (e.g., an IP packet).

The S-TSID represents Service-based Transport Session InstanceDescription. The S-TSID may correspond to a fragment of SLS metadatathat is defined in the form of XML. The S-TSID may include sessiondescription information for transmission sessions for transmittingcontent components included in the ATSC service. The S-TSID may includedescription information of transmission of an object and/or object flowtransmitted through an associated transmission session, or for theS-TSID, reference can be made to the description information.

The TOI represents Transmission Object Identifier. The TOI may betransmitted by an LCT header and may correspond to a unique identifierof a transport object transmitted in an ALC/LCT session.

The TSI represents Transmission Session Identifier. The TSI may be anidentifier of an ALC/LCT transmission session within a range of an IPaddress of a sender and a TSI value.

The USBD/USD represents User Service Bundle Description/User ServiceDescription. The USBD may correspond to an SLS metadata fragment in theform of XML. The USBD may function as an entry point for access to afragment (e.g., S-TSID, MPD, and/or MMTP) included in another SLS. Thatis, the USBD may include information required to access to a fragmentincluded in the SLS. The USBD may identify an ATSC3.0 service andinclude basic information about a service, such as a service name or aservice language. Each USBD may include information about one servicerepresented by userServiceDescription (USD).

The XML Diff represents a difference between two XML files. The XML Diffmay be generated by a sender and may correspond to XML signalingtemplate and/or XML signaling instance which are transmitted to areceiver. The receiver may apply XML Diff to a local copy of a templateowned by the receiver in order to acquire the signaling instance. TheXML Diff mechanism may be a method for replacing a compression tool(e.g., Gzip) for compression of SLS data transmitted via a broadcastnetwork and may be provided by a broadcast system.

A hierarchical signaling structure of a broadcast system according tothe present embodiment may support streaming of two or more differentservice transmission methods. That is, the proposed hierarchicalsignaling structure may provide integrated signaling for servicetransmission of DASH through ROUTE and service transmission of MPUthrough MMTP.

As described above, Low Level Signaling and Service Level Signaling maybe differentiated. The Low Level Signaling may be transmitted as LinkLayer Signaling. The Low Level Signaling may include the aforementionedFIT (or SLT).

The SLS may be transmitted through a broadcast network and in this case,may be processed according to a protocol of ROUTE/UDP/IP. In addition,the SLS may be transmitted through a broadband network and in this case,may be processed according to a protocol of HTTP(s)/TCP/IP.

The SLS may include USBD and/or S-TSID as a signaling structure (orfragment) including information for signaling for a general service.

The SLS may include MPD as a signaling structure (or fragment) includingsignaling information required for content streaming.

The SLS may further include a signaling structure (or fragment) forproviding a service (content or event) that is operated based on anapplication.

Referring to the drawing, when a service is provided based on ROUTEthrough a broadcast network, a receiver may approach the SLS usinginformation of the LLS and acquire DASH representation (or component)for a service using information in an MPD included in the SLS.

When a service is provided based on the MMT through a broadcast network,the receiver may approach the SLS using information of the LLS, acquirean MMT signaling message using information of the SLS, and acquire apacket for transmitting an MMT asset (component) for a service usinginformation in the MMT signaling message.

When a hierarchical signaling structure according to the presentinvention is used, integrated signaling for ROUTE/DASH and MMTP/MPUstreamlining transmission can be provided.

When a hierarchical signaling structure is used, integrated signalingfor hybrid service transmission through a broadcast network and abroadband can be provided.

When a hierarchical signaling structure is used, the standard of 3DPPeMBMS that is conventionally used and next-generation broadcast standardmay be connected to each other so as to acquire connectivity betweenheterogeneous devices.

When a hierarchical signaling structure is used, entire signaling datacan be effectively transmitted/received.

When a hierarchical signaling structure is used, a receiving side mayacquire a desired fragment via simple filtering with respect tobroadcast signaling.

In addition, when a hierarchical signaling structure is used, two ormore compression options for signaling data can be freely used (Gzipand/or XML Diff).

FIG. 55 is a diagram illustrating a transmission path of an FITaccording to an embodiment of the present invention.

A broadcast receiver may access a service from an FIT (or SLT) from astarting point in broadcast emission. The FIT may include theaforementioned information items and provide information required torapidly scan channels in order to write a list of services that thereceiver can receive. In addition, the FIT may include information(bootstrap information) required for access to the SLS by the receiver.As described above, the bootstrap information may include source IPaddress information of a packet for transmitting the SLS, destination IPaddress information, destination port information, TSI information of anLCT session for transmitting the SLS, and/or ID information of a PLP fortransmitting the SLS. However, the PLP ID information as information foridentifying the PLP for transmitting the SLS may be included in theaforementioned first layer signaling (that is, physical layer signalingor L1 signaling).

The FIT may include ID information for identifying one broadcast stream,and the ID information for identifying the broadcast stream may be usedas information for identifying a broadcaster. That is, the FIT may beseparately provided per broadcaster.

The FIT may include a service loop including information for each ofservices provided through a broadcast stream identified by each IDinformation item.

The service loop may include service ID information for uniquelyidentifying a service in a range of a broadcast region, short nameinformation indicating a short name of a service, provider IDinformation (e.g., information for identifying a broadcaster that uses aportion of a broadcast stream when the broadcast stream is shared by aplurality of broadcaster.) for identifying a provider of each service,and/or bootstrap information as information for acquiring the SLS foreach service.

Details of the above information items included in the FIT are replacedby the above or following description.

Referring to the drawing, (1) the FIT may be included in a PLP fortransmitting components included in a service and transmitted, (2) adedicated channel for transmitting an FIT in a physical layer may bedefined and the FIT may be transmitted through a corresponding channel,or (3) main data such as an FIT and a PLP for signaling transmission maybe defined, a method for identifying a corresponding PLP may beprepared, and the FIT may be transmitted to the corresponding PLP.

FIG. 56 is a diagram illustrating a process for bootstrapping an SLSusing an FIT according to an embodiment of the present invention.

A receiver may acquire an FIT that is transmitted through an RF channel(physical layer signal) using the aforementioned method. The drawingillustrates the case in which an LLS (FIT) is transmitted through adedicated channel in a broadcast signal.

The receiver may search for a region of a broadcast signal, to which anSLS for a service that the receiver wants to access, using Service IDinformation, Service Category information, SLS source IP addressinformation, SLS destination IP address information, SLS destinationport number information, SLS PLP ID information, and/or SLS TSIinformation, which are included in the FIT. The SLS may be transmittedin a ROUTE session. That is, the receiver may access a specific regionin the ROUTE session for transmitting the SLS and acquire the SLS usingthe above information included in the FIT.

The receiver may acquire data and signaling information for presentationof a service using USBD, MPD, and/or S-TSID included in the acquiredSLS.

The SLS may be defined per service level and may include information fordescribing access to a service and attribute of the service. Forexample, the information included in the SLS may include information forlisting content components included in the service, information requiredto acquire corresponding components, and information for identifyingcapability required by a receiver in order to present a correspondingcomponent or service.

The SLS may be defined in the form of XML. A dedicated LCT session maybe defined for transmission of the SLS.

The SLS may further include a fragment including signaling informationrequired to provide an application-based service in addition to a USBDfragment, an MPD fragment, and an S-TSID fragment. As described above,the SLS may provide transmission session description informationincluding information for access to a ROUTE session and/or an MMTPsession.

FIG. 57 is a diagram illustrating extension of 3DPP MBMS signaling for abroadcast system according to an embodiment of the present invention.

In a signaling structure for the broadcast system, an SLS may include aUSBD fragment and the USBD fragment may be used in the form defined inthe 3GPP MBMS. In this case, in the USBD defined in the 3GPP MBMS,signaling information required for the broadcast system needs to beadded.

The information to be added to the USBD for the broadcast system mayinclude @atsc:serviceId information, @atsc:sTsidUri information,@atsc:fullMpdUri information, <atsc:capabilityCode> element,<atsc:broadcastAppService> element, <basePattern> element,<atsc:unicastAppService> element, and/or <basePattern> element.

The @atsc:serviceId information may be information for identifying abroadcast service.

The @atsc:sTsidUri information may be information for connection withS-TSID in the USBD. The @atsc:sTsidUri information may be URIinformation for a region to which the S-TSID is transmitted.

The @atsc:fullMpdUri information may be information for connection withMPD in the USBD. The @atsc:fullMpdUri information may be URI informationfor a region to which the MPD is transmitted.

The <atsc:capabilityCode> element may include information foridentifying capability required by a receiver in order to significantlypresent a service or a component by the receiver.

The <atsc:broadcastAppService> element may include signaling informationfor an application-based service, transmitted through a broadcastnetwork, and the <basePattern> element included below the<atsc:broadcastAppService> element represents a base pattern of URIrequired to acquire a corresponding application-based service.

The <atsc:unicastAppService> element may include signaling informationfor an application-based service transmitted through a unicast network,and the <basePattern> element included below the<atsc:unicastAppService> element may represent a base pattern of URIrequired to acquire a corresponding application-based service.

The @atsc:serviceId information may have 16 bits and may be used forlink with a service ID included in the FIT.

The USD may include service level description that cannot be included inthe FIT. Since the FIT has limited capacity, the FIT cannot unlimitedlyinclude signaling information of a service level, and thus the signalinginformation of a service level that cannot be included in the FIT may beincluded in the USD. The information may include information indicatingservice names represented by different languages, information (or amethod for transmitting a component may be determined by a basePatternelement used as a matching pattern corresponding to a segment URLrequested by a DASH client) for identifying whether each servicecomponent is transmitted through a broadcast network or a broadbandnetwork, information identifying performed required by a receiver,content advisory related information, caption description information,and/or information that needs to be extended for an ATSC3.0 broadcastsystem.

The S-TSID may include entire session description of transmissionsession(s) for transmitting a content component of an ATSC service.

In order to transmit a linear service that does not includeapplication-based enhancement through a broadcast network, the S-TSIDmay include information (when service components are transmitted throughROUTE) for describing an LCT session and/or information (when servicecomponents are transmitted through MMTP) for describing an MMTP session.The application-based enhancement may be provided alone as an event,content, and/or a service which are provided based on an application ormay be used together with a linear service for providing an additionalservice/content/event for the linear service

When service components are streamed through ROUTE, the S-TSID mayinclude file metadata for transmitting an object or object flowtransmitted by an LCT session of a service, and/or additionalinformation for content components transmitted by LCT sessions and apayload format.

The SLS may be transmitted through an ALC/LCT session of a ROUTEsession. A fragment (service signaling fragment) included in the SLS maybe encapsulated in the form of metadata envelope defined in the 3GPPMBMS, and this form may include identifying information, versioninformation, update information, and/or compression information about afragment. The receiver may use a filtering scheme that employs an LCTpacket including a filtering parameter for an effective packetcombination.

The service signaling fragment may be compressed using a Gzip and/ortemplate/Diff-based compression method. When the template/Diff-basedcompression method is used, as described above, the size of signalingmay be reduced, and change such as partial update of signaling may bemade, thereby obtaining efficiency in terms of data transmission anddata processing of the receiver.

When the service signaling fragment is compressed using thetemplate/Diff-based compression method, the signaling template may bepre-shared by a transmitting end and a receiver end. In this case, thetransmitting end may compare signaling instance that needs to betransmitted with a template to generate Diff. The transmitting end maytransmit the Diff to a client. The receiving end may apply the Diff tothe template to acquire signaling instance. In this manner, when adifference between the template and a complete fragment is very small, abroadcast system may be effectively operated in terms of datatransmission and data processing compared with a compression method suchas Gzip.

FIG. 58 is a diagram illustrating a protocol stack of a broadcast systemaccording to an embodiment of the present invention.

An ATSC3.0 service may be transmitted using three functional layers.These may include a physical layer, a delivery layer, and a servicemanagement layer. The physical layer may provide a mechanism fortransmitting signaling transmitted through a broadcast physical layerand/or a broadband physical layer, service announcement, and IP packets.The delivery layer may provide object and object flow transmittingfunctionality. That is, in the delivery layer, the ROUTE protocol,operating on a UDP/IP multicast over the broadcast physical layer may beperformed, and the HTTP protocol on a TCP/IP unicast over the broadbandphysical layer may be performed. The service management layer enablesany type of service, such as linear TV or HTML5 application service, tobe carried by the underlying delivery and physical layers.

The service signaling provides information for service discovery anddescription. The service signaling may include two functionalcomponents. One of the two functional components may be bootstrapsignaling (FIT—Fast Information Table or SLT—Service List Table) and theother one may be service layer signaling (SLS). The service signalingmay be information items required to discover and acquire user services.The FIT may enable the receiver to generate a basic service list and toperform bootstrapping for discovery of the SLS for each ATSC3.0 service.The FIT may be transmitted from a link layer or an upper layer thereofand transmitted per frame of a physical layer for rapid acquisition. TheSLS may enable a receiver to discover and access ATSC3.0 services andcontent components thereof. When the SLS is transmitted through abroadcast network, the SLS may be transmitted through ROUTE/UDP/IPincluded in one of LCT transmission sessions including a ROUTE sessionat a carousel rate that is appropriate to support rapid channelsubscription and switching. When the SLS is transmitted through abroadcast network, the SLS may be transmitted through HTTP(s)/TCP/IP.

FIG. 59 is a diagram illustrating a relationship of a service managementlayer, a delivery layer, and physical layer entities according to anembodiment of the present invention.

In a broadcast system according to the present invention, in order totransmit content components of an ATSC3.0 service, a ROUTE/LCT sessionand/or MMTP sessions may be present.

In order to transmit a linear service that does not includeapplication-based enhancement, content components included in theservice may be transmitted through one or more ROUTE/LCT sessions or oneor more MMTP sessions.

In order to transmit a linear service that includes application-basedenhancement, content components of the service may be transmittedthrough one or more ROUTE/LCT sessions or zero or more MMTP sessions.That is, in this case, some of content components constituting oneservice may be transmitted through a ROUTE/LCT session and other some ofthe content components may be transmitted though a MMTP session. Forexample, content components included in application-based enhancementcan be transmitted only through ROUTE, and thus when even a service thatbasically applies MMTP includes application-based enhancement, ROUTE mayneed to be used in order to transmit some components. However, forstreaming of a media component in the same service, it may not bepermitted that both the MMTP and the ROUTE are used.

In order to transmit an application service through a broadcast network,content components included in the service may be transmitted throughone or more ROUTE/LCT sessions.

Each ROUTE session may include one or more LCT sessions for transmittingsome or all of content components constituting an ATSC3.0 service. Intransmission of a streaming service, one LCT session may transmit oneseparate component of a user service such as audio, video, or closedcaption stream. The streaming media may be formatted and transmitted nthe form of DASH segments of MPEG DASH.

Each MMTP session may transmit all or some of content components or mayinclude one or more MMTP packet flows for transmitting an MMTP signalingmessage. One MMTP packet flow may transmit a component or MMT signalingmessage in the form of MPU of MMT. In order to transmit an NRT userservice or system metadata, an LCT session may transmit a file-basedcontent item. Files included in the contents may include a mediacomponent of a continuous or time-based or discrete or non-time-basedNRT service or may include metadata such as service signaling or ESGfragment.

A broadcast stream may be concept for an RF channel and may be definedas a term of a center carrier frequency in a specific bandwidth. Thebroadcast stream may be identified by a geographic area and a frequency.Together with a pair of a geographic area and frequency information, abroadcast stream ID (BSID) of the pair may be defined and managed byadministrative power. The PLP may correspond to a portion of the RFchannel. Each PLP may have a specific modulation and coding parameter.The PLP may be identified by a unique PLP identifier (PLP ID) in abroadcast stream to which the PLP belongs.

Each service may be identified by two types of service identifiers. Oneof the service identifiers may be a compact type service identifier thatis used in a FIT and is unique only in a broadcast stream, and the otherone may be a unique type service identifier that is used in SLS and ESGand is unique around the world. One ROUTE session may be identified by asource IP address, a destination IP address, and a destination portnumber. One LCT session (which is related to a service component fortransmitting the LCT session) may be identified by a unique transportsession identifier (TSI) within a range of a ROUTE session to which theLCT session belongs.

Common features to LCT sessions and unique specific features to therespective LCT sessions may be given in a ROUTE signaling structure thatis referred to as service-based transport session instance description(S-TSID). The S-TSID is a portion of service level signaling. Each LCTsession may be transmitted through one PLP. Different LCT sessions ofone ROUTE session may or may not be included in different PLPs. Featuresdescribed in the S-TSID may include a TSI value, a PLP ID for each LCTsession, a descriptor for transmitting an object/file, and/or anapplication layer FEC parameter.

One MMTP session may be identified by a destination IP address and adestination port number. One MMTP packet flow (which is related toservice components for transmitting the MMTP packet flow) may beidentified by a unique packet_id in a range of a MMTP session includingthe MMTP packet flow. Common features to the MMTP packet flows andspecific feature of each MMTP packet flow may be given by the S-TSID.Features for the respective MMTP sessions may be given by a MMTsignaling message transmitted in the MMTP session. Each MMTP packet flowmay be transmitted through one PLP. Different MMTP packet flows of oneMMTP session may or may not be transmitted through different PLPs.Features described in the MMT signaling message may include a packet_idvalue and/or a PLP ID for each MMTP packet flow.

Information for identifying a PLP that is described as being included inthe service level signaling or an FIT (or SLT) may be defined insignaling of a link layer. In this case, upon acquiring signalingtransmitted to a link layer, a receiver may identify or access an FIT(or SLT), service level signaling, or a PLP related to a component.

FIG. 60 is a diagram illustrating a signaling structure of a broadcastsystem according to an embodiment of the present invention.

Signaling information transmitted through a payload of a packet of alink layer (or an upper layer thereof) or content of a dedicated channelmay be referred to as link layer signaling (LLS) or low level signaling(LLS). The aforementioned FIT (or which may be referred to as a servicelist table (SLT)) may be classified as an LLS. The FIT may be similar toa program association table (PAT) defined in the MPEG-2 system or a fastinformation channel (FIC) defined in the ATSC-MH in terms of a function.Upon receiving a transmitted broadcast stream, a receiver may processdata or a service from an FIT as a starting point. The FIT may supportthe receiver to rapidly scan channels. That is, the FIT may includeinformation required to generate a list of all services that can bereceived by the receiver. The information may include information suchas a channel name and/or a channel number. In addition, the FIT mayinclude bootstrap information such that the receiver discovers an SLSfor each service. The bootstrap information may include TSI informationof an LCT session for transmitting an SLS, a source IP address of aROUTE session, a destination IP address, and/or destination poet numberinformation.

An SLS for each service may describe attributes of services. Forexample, the SLS may include a list of components included in a service,information about where a corresponding component is acquired, and/orinformation about capability required by a receiver in order tosignificantly present a corresponding service. In a ROUTE/DASH system,the SLS may include user service bundle description (USBD), S-TSID, andDASH media presentation description (MPD). The USBD may be based on aservice description metadata fragment having the same term as a termdefined in the 3GPP-MBMS, may have a form that is extended in acorresponding metadata fragment in order to support a function of anATSC3.0 system, and may be defined to have compatibility with the3GPP-MBMS in the future. Details of information included in the USBD maybe replaced by the above or following description of the USBD (or USD).

The service signaling may focus on basic attribute of a service per se.In particular, the service signaling may focus on content aboutattributes required to acquire a service. An intended program forfeatures and viewers of a service may be represented by, for example,service announcement or ESG data.

When there is separate for service signaling for each service, areceiver may be permitted to acquire an SLS appropriate for an interestserviced without parsing of all SLS transmitted in a broadcast stream.

The service signaling may also be transmitted through a broadband and inthis case, the FIT may include a HTTP URL about a position in which aservice signaling file (a file including service signaling).

When an even such as update occurs in SLS signaling, the correspondingevent may be detected by an “SLS version” field included in the FIT. Theupdated signaling may be acquired by a broadcast network or a broadbandnetwork.

The drawing illustrates an embodiment in which an SLS is used in orderto perform bootstrap for acquisition of the SLS using LLS and to acquireservice components transmitted through a ROUTE/LCT transmission session.The receiver may begin to acquire an FIT transmitted by a physical layerframe in a determined frequency band identified by a broadcast stream ID(BSID). With respect to each service identified by Service_id, SLSbootstrapping information—PLPID(#1), source IP

(siP1), destination IP address (diP1), destination port number (dPort1),and TSI (tsi-SLS) may be provided. The receiver may acquire bootstrapstransmitted through the PLP and the IP/UDP/LCT session. The fragmentsmay include a USBD/USD fragment, an S-TSID fragment, and a MPD fragment.These may be fragments for transmitting metadata related to one service.The USBD/USD fragment may describe features of a service level andprovide a URI for access to the S-TSID fragment and a URI for access tothe MPD fragment. The S-TSID fragment may be related to one service andcomponent acquiring information for providing mapping informationbetween DASH representation included in the MPD and TSI corresponding toa component of the corresponding service. The S-TSID may providecomponent acquiring information in the form of an ID of a PLP fortransmitting DASH segments related to DASH representation, TSI, andrelated DASH representation identifier. Using PLPID and TSI values, thereceiver may collect audio/video components of a service, begin tobuffer DASH media segments, and perform a proper decoding procedure.

A hierarchical signaling structure including two separated S-TSIDfragments for providing access information for LCT sessions fortransmitting contents of one separate service will be described later.

Service signaling may provide bootstrap and discovery information for abroadcast service that is currently “on-the-air”. The broadcast servicethat is currently “on-the-air” may correspond to, for example, a linearTV service. The ESG may include user service announcement indicating alist of contents and available ATSC3.0 user services together withdetailed information including capability required for a device, contentrating, and show schedule. The information may be required by an EGSclient in the receiver in order to show services or content to a userfor service or content selection or to determine whether relatedservices or content are configured to be shown to the user. Connectionbetween an ESG service and an SLS service may be performed by a serviceidentifier. This may be, particularly, a key for identifying serviceattributes in the ESG as well as a key for identifying serviceattributes including transmission related attributes in signaling.

The link layer signaling may be operated under an IP level or less. Areceiving end may more rapidly acquire link layer signaling than IPlevel signaling (e.g., service layer signaling). The link layersignaling may be acquired prior to establishment of a session.

One of purposes of link layer signaling may be effective transmission ofinformation required to rapidly scan a channel and to acquire a service.The information may include information for mainly binding betweenATSC3.0 service layer signaling and PLPs. The link layer signaling mayfurther include signaling related to emergency alert. The link layersignaling may be encapsulated through a protocol of a link layer and maycorrespond to signaling to be acquired when the protocol of the linklayer is performed.

The link layer signaling may also be referred to as low level signaling.Although the link layer signaling has been described as signaling to beacquired in a lower level than an IP level, when a dedicated channel forcorresponding signaling is generated in a broadcast signal, the linklayer signaling may be defined in a higher level of the IP level. Inthis case, the receiver may be pre-access link layer signaling comparedwith service layer signaling using an IP address and/or UDP port numberallocated to a corresponding dedicated channel.

The service layer signaling (or which may be referred to as servicelevel signaling) (SLS) may include USBD and S-TSID metadata fragment.These service signaling fragments may be applied to both a linearservice and an application-based service. The USBD fragment may includea service identifier, device capability information, information forreferring to other SLS fragments required to access a service and amedia component included therein, and/or metadata formed to allow thereceiver to determine a transmission mode (broadcast networktransmission and/or broadband transmission) of servicer components. TheS-TSID fragment referred to by the USBD may include a transmissionsession descriptor for one or more ROUTE/LCT sessions or MMTP sessionsfor transmitting media content components of one ATSC3.0 service anddescription of transmission objects transmitted by LCT sessions.

A component (fragment) for signaling streaming content in the SLS maycorrespond to an MPD fragment. The MPD may be general streaming contentand may be related to a linear service for transmitting DASH segments.The MPD fragment may be used to support application-based services orneeds to be associated with content components of a DASH format. The MPDmay include information items required to control reproduction ofcontents. The MPD may provide a resource identifier for separate mediacomponents for a linear or streaming service in the form of a segmentURL and provide context identified resources in media presentation.

The application-based enhancement signaling may include information fortransmitting of application-based enhancement components such as anapplication logic file, an NRT media file, an on-demand contentcomponent, or a notification stream. An application may acquire NRT datavia broadband connection.

A sequence of accurate wall clock references may be transmitted througha physical layer for synchronization between services, components, orevents.

Service signaling of a service may be transmitted in an ALC/LCT sessionin a ROUTE session. The service signaling fragment may be encapsulatedas a metadata envelope defined in the 3DPP MBMS. This type ofencapsulation may enable identification, versioning, and updating of anincluded fragment. The metadata envelope and the included fragment maybe compressed via Gzip. In addition, the receiver may use atemplate-based method.

The receiver may signal the type and version of a signaling fragment ofa service layer signaling fragment and filter the signaling fragment.Prior to acquisition of all service layer signaling fragments frompackets using this method, a target LCT packet for transmitting anexpected type of service layer signaling fragment may be rapidlyfiltered. This method may be performed by defining a TOI structure of anLCT header, which will be described later.

FIG. 61 is a diagram illustrating an FIT according to an embodiment ofthe present invention.

In the present invention, the FIT may be used as the term of FIC, SLT,low level signaling (LLS), or the like. In addition, the FIT may bedefined as one signaling structure included in the LLS. In this case,some of information included in the FIT disclosed in the embodiment ofthe present invention may be included in the LLS. The LLS may correspondto signaling information transmitted through a payload of an IP packethaving a well-known address/port in a broadcast system.

The illustrated FIT may correspond to a signaling structure forsupporting broadcast service scan and acquisition in a receiver. To thisend, FIT may include a sufficient amount of information that issignificant to viewers and allows presentation of a service list forsupporting service selection through channel number and/or up/downzapping. In addition, the FIT may include a sufficient amount ofinformation for locating service layer signaling of a service through abroadcast network or a broadband network according to where signalingcan be used.

In a specific frequency, broadcast services and/or content generated byone or more broadcasters may be transmitted. In this case, in order toallow the receiver to rapidly and easily scan a broadcaster present in acorresponding frequency and/or services and/or content of thecorresponding broadcaster. In this process, required information may besignaled through the FIT.

When the signaling structure proposed according to the present inventionis used, the receiver can scan a service and reduce velocity foracquisition of a service by the receiver. The illustrated FIT has beendescribed as syntax but information included in the FIT may berepresented in other formats such as XML.

In the present invention, a fast information table (FIT) may betransmitted through a fast information channel (FIC) as a separatechannel in the physical layer transport frame. Alternatively, the FITmay be transmitted through a common DP or the like for transmittinginformation to be shared between data pipes of a physical layer.Alternatively, the information included in the FIT may be transmittedvia a path for transmitting link layer signaling defined in a link layeror link layer signaling. Alternatively, the FIT may be transmittedthrough a service signaling channel for transmitting service signaling,a transport session of an application layer, or the like.

A FIT according to an embodiment of the present invention may includeFIT_protocol_version information, Broadcast_stream_id information,FIT_section_number information, total FIT_section_number information,FIT_section_version information, FIT_section_length information,num_services information, service_id information, SLS_data_versioninformation, service_category information, short_service_name_lengthinformation, short_service_name byte_pair( ) element, provider_idinformation, service_status information, sp_indicator information,num_service_level_descriptor information, service_level_descriptor( )element, num_FIT_level_descriptor information, and/orFIT_level_descriptor( ) element.

The FIT_protocol_version information may be information indicating aversion of an FIT structure.

The Broadcast_stream_id information may be information for identifyingall broadcast streams.

The FIT_section_number information may be information indicating anumber of this section. The FIT may include a plurality of FIT sections.

The total_FIT_section_number information may be information indicatingthe number of all FIT sections of a FIT including this section as apart. The information may be the same as FIT_section_number informationwith a highest value.

The FIT_section_version information may be information indicating aversion number of a FIT section. A value of the information may beincreased on 1-by-1 basis when information transmitted in the FITsection is changed. When a value of the information reaches a maximumvalue, the value of the information may return to 0.

The FIT_section_length information may be information indicating a bytenumber of an FIT section including information items subsequent to theinformation.

The num_services information may be information indicating the number ofservices described by an instance of a FIT. Services having at least onecomponent may be included in each broadcast stream.

The service_id information may be information indicating a number foruniquely identifying a service within a range of a broadcast area.

A value of the SLS_data_version information may be increased at a timepoint when any one of signaling tables for a service transmitted throughservice layer signaling is changed or when a service entity for servicesin the FIT is changed. The information may allow a receiver to observethe FIT and to know change when signaling for a service is changed.

The service_category information may be information for identifying acategory of a service. When a value of the information is ‘0x00’, thevalue may indicate that a category of the service cannot be identifiedby the information, when the value is ‘0x01’, the value may indicatethat the service corresponds to an audio/video (A/V) service, when thevalue is ‘0x02’, the value may indicate that the service corresponds toan audio service, when the value is ‘0x03’, the value may indicate thatthe service is an application-based service, and when the value is‘0x01’ and the value is ‘0x08’, the value may indicate that the serviceis a service guide (service announcement). Other values to be allocatedto the information may be reserved for future use.

The provider_id information may be information may be information foridentifying a provider for broadcasting a service.

The short_service_name_length information may be information indicatingthe number of bytes in the short_servicenamebyte_pair( ) element. When ashort name for a service is not provided, a value of the information maybe 0.

The short_service_name_byte_pair( ) element may be informationindicating a short name of the service. Each character may be encoded inthe form of UTF-8. When an odd byte is present in the short name, asecond byte of a last byte pair may include 0x00 per pair countidentified by the short_service_name_length information.

The service_status information may be information indicating a servicestate (active/inactive and/or hidden/shown). An uppermost bit of theservice_status information may indicate whether a service is in anactive state (the bit is set to 1) or the service is in an inactivestate (the bit is set to 0). A lowermost bit of the service_statusinformation may indicate may indicate whether a service is in a hiddenstate (the bit is set to 1) or is in a shown state (the bit is set to0).

Upon being set to a predetermined value, the sp_indicator informationmay be information for identifying whether one or more componentsrequired to significant presentation are protected. When a value of theinformation is set to ‘0’, the information may indicate that there is nocomponent to be applied to be protected among components required forsignificant presentation of a service.

The num_service_level_descriptor information may be informationindicating the number of service level descriptors for a service.

The service_level_descriptor( ) element may include zero or more servicelevel descriptor for providing additional information for a service.

The num_FIT_level_descriptor information may be information indicatingthe number of FIT level descriptors for an FIT.

The FIT_level_descriptor( ) element may include zero or more descriptorsfor providing additional information for an FIT.

FIG. 62 is a diagram illustrating a position of a descriptor to beincluded in signaling for a broadcast system according to an embodimentof the present invention.

Zero or more descriptors for providing additional information for aservice or an FIT may be included in a signaling structure.

The descriptor illustrated in the drawing may indicate a name andposition of a descriptor to be contained in an FIT level descriptor or aservice level descriptor in an FIT.

The FIT may include broadcast_signaling_location_descriptor( ),inet_signaling_location_descriptor( ), and/or capability_descriptor( ).

The broadcast_signaling_location_descriptor( ) may be included in aregion for signaling information about a position in which the servicelevel descriptor of the FIT is included or a service.

The inet_signaling_location_descriptor( ) may be included in a positionin which the service level descriptor of the FIT is contained or aposition in which the FIT level descriptor is contained.

The capability_descriptor( ) may be included in a region for signalinginformation about a position in which the service level descriptor ofthe FIT is positioned or a service.

FIG. 63 is a diagram illustratingbroadcast_signaling_location_descriptor( ) according to an embodiment ofthe present invention.

The broadcast_signaling_location_descriptor( ) may include informationfor bootstrapping an address of service layer signaling for eachservice, and a receiver may acquire an SLS transmitted through abroadcast network at a corresponding address.

The broadcast_signaling_location_descriptor( ) may include descriptortag information, descriptor length information, IP_version_flaginformation, SLS_source_IP_address_flag information,SLS_source_IP_address information, SLS_destination_IP_addressinformation, SLS_destination_UDP_port information, SLS_TSI information,and/or SLS_PLP_ID information.

The descriptor tag information may be information for identifying adescriptor.

The descriptor length information may be information that is included ina descriptor and indicates a size (length) of information itemssubsequent to the information.

The IP_version_flag information may be information indicating a versionof an IP used in an IP address transmitted in the present descriptor.When a value of the information is set to ‘0’, the SLS_source_IP_addressinformation and the SLS_destination_IP_address information may indicatean IPv4 address, when a value of the information is set to ‘1’, theSLS_source_IP_address information and the SLS_destination_IP_addressinformation may indicate an IPv6 address.

The SLS_source_IP_address_flag information may be information foridentifying whether the SLS_source_IP_address information is present.

The SLS_source_IP_address information may indicate a source IP addressof packets for transmitting an SLS.

The SLS_destination_IP_address information may indicate a destination IPaddress of packets for transmitting an SLS.

The SLS_destination_UDP_port information may indicate a port number of adestination of packets for transmitting an SLS.

The SLS_TSI information may be information for identifying atransmission session for transmitting an SLS.

The SLS_PLP_id information may be information for identifying aposition/region for transmitting an SLS. The SLS_PLP_id information maybe information for identifying a PLP including an SLS. The SLS_PLP_idinformation may be included in link layer signaling and transmitted. Inthis case, depending on cases, the information may be contained insignaling transmitted in a link layer and may be transmitted.

FIG. 64 is a diagram illustrating the meaning ofinet_signaling_location_descriptor( ) and URL_type information accordingto an embodiment of the present invention.

The inet_signaling_location_descriptor( ) may include a URL indicating aplace for receiving a type of data, requested by an external server,through a broadband by a receiver. The receiver may use one URL includedin the present descriptor as a query term for acquiring signalingdescription through a broadband.

The inet_signaling_location_descriptor( ) may include descriptor taginformation, descriptor_length information, provider_id information,URL_type information, and/or URL_bytes( ) information.

The descriptor_tag information may be information for identifying thedescriptor.

The descriptor length information may be information that is included ina descriptor and indicates a size (length) of information itemssubsequent to the information.

The provider_id information may be information for identifying aprovider for broadcasting a service.

The URL_type information may be information indicating a type of a URLrepresented by URL_bytes( ). When a value of the information is “0x00”,the value may indicate that the represented URL is a URL of a signalingserver for providing the signaling, and when a value of the informationis “0x01”, the value may indicate that the represented URL is a URL ofan ESG server for providing the ESG data.

The URL_bytes( ) information may indicate a uniform resource location(URL), and each character included in the URL may encoded using a UTF-8method. The URL may be used as a query term, and a base URL may beextended by a query term in order to indicate a resource.

When resources can be used through a broadband network, theinet_signaling_location_descriptor( ) may provide URL information aboutthe resources.

FIG. 65 is a diagram illustrating a query term using URL_bytesinformation of inet_signaling_location_descriptor( ) according to anembodiment of the present invention.

The inet_signaling_location_descriptor( ) may be positioned in an FITlevel, and a URL may be used as a query term indicating a type of aresource requested by the URL. When a type of a resource corresponds toan SLS, a URL indicating where a receiver acquires an SLS through abroadband for all services described in an FIT may be included in theinet_signaling_location_descriptor( ). In this case, optionally, (svc)string may be used, and the (svc) string can be added to a last portionof the query term to request an SLS for a specific service by areceiver. A reply to the query term may have an SLS fragmentencapsulated as a multi part.

When a type of a resource is an ESG a URL indicating where a receiveracquires ESG through a broadband for all providers described in the FITmay be included in inet_signaling_location_descriptor( ). In this case,optionally, (prv) string may be used, and the (prv) string can be addedto a last portion of the query term to request an ESG for a specificprovider by a receiver.

The inet_signaling_location_descriptor( ) may be transmitted through aloop for a service level descriptor, and in this case, theinet_signaling_location_descriptor( ) may indicate a URL of a positionin which service layer signaling included in a service is acquiredthrough a broadband. When the service_category information indicatesthat a category of a service indicates an A/V service, the URL may beused as a query term indicating desired signaling description. When abroadcaster provides different SLS URLs for respective services, thisquery term may be used, and in this case, a query term of adding the(svc) string may not be used. A reply to the query term may have an SLSfragment encapsulated as a multi part.

An upper portion of the drawing illustrates an embodiment of a queryterm using URL_bytes information when theinet_signaling_location_descriptor( ) is positioned in an FIT level, anda lower portion of the drawing illustrates an embodiment of a query termusing URL_bytes information when the inet_signaling_location_descriptor() is positioned in a service level.

The query term according to an embodiment of the present invention maybe used as SLS Set—a query for requesting all SLSs, SLS Diff—a query forrequesting Diff data of an SLS, SLS Template—a query for requesting SLStemplate, USD—a query for requesting USD, S-TSID—a query for requestingS-TSID, and/or ESG—a query for requesting ESG

FIG. 66 is a diagram illustrating capability_descriptor( ) according toan embodiment of the present invention.

The capability_descriptor( ) may provide a list of “capabilities” (e.g.,a download protocol, an FEC algorithm, a wrapper/archive format, ancompression algorithm, and a media type) used for one service. Areceiver may parse and process capability_descriptor( ), and whenrequired capability identified by information in thecapability_descriptor( ) cannot be supported, requirement for acorresponding service may be avoided.

The capability_descriptor( ) may include descriptor_tag information,descriptor_length information, and/or capabilities_bytes( ) element.

The descriptor_tag information may be information for identifying thedescriptor.

The descriptor_length information may be information that is included inthe descriptor and indicates a size (length) of information itemssubsequent to the information.

The capabilities_bytes( ) element may indicate information aboutcapability of a string type. Information items to be contained in theaforementioned capability_descriptor may be included in the capabilitiesbytes( ) element.

FIG. 67 is a diagram illustrating an FIT defied in XML according to anembodiment of the present invention.

The FIT defined in XML may include @bsid information, @fitSectionNumberinformation, @totalFitSectionNumber information, @fitSectionVersioninformation, Service element, @serviceId information, @providerIdinformation, @serviceCategory information, @spIndicator information,@serviceStatus information, @shortServiceName information, @SLSVersioninformation, capabilityCode element, inetSignalingLocation element,@urlType information, @url information, broadcastSignalingLocationelement, @IPVersion information, @sourceIPAddress information,@destinationIPAddress information, @destinationUdpPort information, @TSIinformation, @PLPID information, inetSignalingLocation element,@providerId information, @urlType information, and/or @url information.

The @bsid information may be information for identifying a broadcaststream.

The @fitSectionNumber information may be information indicating a numberof the section. The FIT may include a plurality of FIT sections.

The @totalFitSectionNumber information may be information indicating thenumber of all FIT sections of an FIT that includes the section as apart. The information may be the same as the FIT_section_numberinformation with a highest value.

The @fitSectionVersion information may be information indicating aversion number of an FIT section. A value of the information may beincreased on 1-by-1 basis when information transmitted in the FITsection is changed. When a value of the information reaches a maximumvalue, the value of the information may return to 0.

The service element may be an ATSC3.0 service entry. The service elementmay include information related to an ATSC3.0 service.

The @serviceId information may be information indicating a number foruniquely identifying a service within a range of a broadcast area.

The @providerId information may be information for identifying aprovider for broadcasting a service.

The @serviceCategory information may be information for identifying acategory of a service. When a value of the information is ‘0x00’, thevalue may indicate that a category of a service is not identified by theinformation, when the value is ‘0x01’, the value may indicate that aservice corresponds to an audio/video (A/V) service, when the value is‘0x02’, the value may indicate that a service corresponds to an audioservice, when the value is ‘0x03’, the value may indicate that a servicecorresponds to an application-based service, and when the value is‘0x01’ and the value is ‘0x08’, the value may indicate that a service isa service guide (service announcement). Other values to be allocated tothe information may be reserved for future use.

Upon being set to a predetermined value, the @spIndicator informationmay be information for identifying whether one or more componentsrequired for significant presentation are protected. When a value of theinformation is set to ‘0’, the information may indicate that there is nocomponent to be applied to be protected among components required forsignificant presentation of a service.

The @serviceStatus information may be information indicating a state(active/inactive and/or hidden/shown) of a service. The information mayindicate whether a service is active (when a value is set to ‘1’),inactive (when a value is set to ‘0’), hidden (when a value is set to‘3’), or shown (when a value is set to ‘2’).

The @shortServiceName information may be information indicating a shortname of a service.

A value of the @SLSVersion information may be increased at a time pointwhen any one of signaling tables for a service transmitted throughservice layer signaling is changed or when a service entity for servicesin the FIT is changed. The information may allow a receiver to observethe FIT and to know change when signaling for a service is changed.

The capabilityCode element may include information indicating acapability group and capability required by a receiver in order togenerate significant presentation of content of an ATSC3.0 service. Thepresent element may include some or all of information to be containedin the aforementioned capability_descriptor.

The inetSignalingLocation element may include a URL indicating a placefor receiving a type of data, requested by an external server, through abroadband by a receiver. The inetSignalingLocation element may includesome or all of information items included in the aforementionedinet_signaling_location_descriptor( ).

The @urlType information may be information indicating a type of a URL.When a value of the information is “0x00”, a represented URL is a URL ofa signaling server for providing the signaling, and when the value ofthe information is “0x01”, the represented URL is a URL of an ESG serverfor providing the ESG data.

The @url information may be information indicating a URL of a positionin which service layer signaling belonging to a service can be acquired.When a category of a service is not an ESG service, a URL may be used asa query term for indicating a desired signaling fragment. When abroadcaster provides different SLS URLs for respective services, acorresponding URL may be used and (svc) string may not be used in aquery term. A base URL may indicate desired resources and may beextended by one or more query terms, an embodiment of which is the sameas the above description. When a category of a service is an ESGservice, the URL may indicate an Internet server for acquiring an ESG

The broadcastSignalingLocation element may include information forbootstrapping an address of service layer signaling for each service,and a receiver may acquire an SLS transmitted through a broadcastnetwork at a corresponding address.

The @IPVersion information may be information indicating a version of anIP used in an IP address. According to setting of a version of theinformation, the information may indicate whether theSLS_source_IP_address information and the SLS_destination_IP_addressinformation are an IPv4 address or an IPv6 address.

The @sourceIPAddress information may indicate source IP addresses ofpackets for transmitting an SLS.

The @destinationIPAddress information may indicate a destination IPaddress of packets for transmitting an SLS.

The @destinationUdpPort information may indicate a port number of adestination of packets for transmitting an SLS.

The @TSI information may be information for identifying a transmissionsession for transmitting an SLS.

The @PLPID information may be information for identifying aposition/region for transmission an SLS. The @PLPID information may beinformation for identifying a PLP including an SLS. The @PLPIDinformation may be included in link layer signaling and may betransmitted. As necessary, the information may be included in signalingtransmitted in a link layer and may be transmitted.

The inetSignalingLocation element may include a URL indicating a placefor receiving a type of data, requested by an external server, through abroadband by a receiver. The inetSignalingLocation element may includesome or all of information items included in the aforementionedinet_signaling_location_descriptor( ).

The @providerId information may be information for identifying aprovider for broadcasting the service.

The @urlType information may be information indicating a type of a URL.When a value of the information is “0x00”, the value may indicate that arepresented URL is a URL of a signaling server for providing thesignaling, and when a value of the information is “0x01”, a representedURL is a URL of an ESG server for providing the ESG data.

The @url information may be information indicating URL of a position inwhich service layer signaling belonging to a service can be acquired.Details of the @url information may be the same as details of theURL_bytes information of the inet_signaling_location_descriptor( ).

LLS according to an embodiment of the present invention may includeemergency alert description (EAD) and rating region description (RRD).

EAD may be referred to as an emergency alert table (EAT) and may includeinformation for emergency alert.

RRD may be referred to as a rating region table (RRT) and may includeinformation related to view restriction.

FIG. 68 is a diagram illustrating a data model for a linear serviceaccording to an embodiment of the present invention.

Service layer signaling (SLS) may provide technical information requiredto discover and access an ATSC3.0 user service and content componentsthereof by a receiver. The service layer signaling may include a set ofmetadata fragments coded in the form of XML, which can be transmittedthrough a dedicated LCT session. The LCT session for transmitting an SLSmay be acquired using bootstrapping information included in the FIT asdescribed above. The SLS may be defined per service level and maydescribe access information and attribute for a service, such asinformation about a list of content components of a service and how thecomponents are acquired. In addition, the SLS may include informationabout receiver capability required to generate significant presentationof a service. In a ROUTE/DASH system, for linear service transmission,the SLS may include a USBD, an S-TSID, and/or a MPD. SLS fragments maybe transmitted through a dedicated LCT transmission session having apre-known TSI value.

Referring to the drawing, the USBD may include USD and the USD mayinclude fullMPDUri information as information for acquiring an MPD. Areceiver may acquire an MPD using the fullMPDUri information. The USDmay include information for connection of S-TSID related to a specificservice, and the receiver may acquire information of the correspondingS-TSID in order to present a specific service using the information.

FIG. 69 is a diagram illustrating USBD according to an embodiment of thepresent invention.

User Service Bundle Description (USBD) may be an entry point oruppermost level fragment of an SLS fragment. The USBD may be conformableto basic content of the USD defined in the 3GPP MBMS and may include thefollowing extension for an ATSC3.0 service.

The USBD may be a child element and may include atsc:servicedinformation, atsc:fullMPDUri information, atsc:sTSIDUri information,and/or atsc:capabilityCode information below the userServiceDescriptionelement.

The USBD may include atsc:broadcastAppService information as a childelement, and broadcast stream ID (BSID) and basePattern element as childattribute thereof, below the deliveryMethod element.

The USBD may include atsc:unicastcastAppServiceand information as achild element and/or basePattern element as a child element thereofbelow the deliveryMethod element.

The USBD may have a bundleDescription ROUTE element. ThebundleDescription ROUTE element may have a userServiceDescriptionelement. The userServiceDescription element may be instance for oneservice.

The userServiceDescription element may include @serviceId,@atsc:serviceId, @atsc:fullMPDUri, @atsc:sTSIDUri, name,serviceLanguage, atsc:capabilityCode, and/or deliveryMethod.

The @serviceId may be a unique service around the world.

The @atsc:serviced may be a reference of a corresponding service entryin the LLS (FIT or SLT). A value of corresponding attribute may be thesame as a value of serviced allocated to a corresponding entry definedin the LLS.

The @atsc:fullMPDUri may be information for referencing (or connecting)an MPD fragment including description of a content component of aservice that is optionally transmitted in broadcast and is transmittedin a broadband.

The @atsc:sTSIDUri may be information for referencing (or connecting) aS-TSID fragment for providing an access related parameter to atransmission session for transmitting content of a correspondingservice.

The name may be a name of a service given according to lang attribute.The name element may include lang attribute indicating a languageindicating a service name. A language may be specified according to atype of XML data.

The serviceLanguage may indicate an available language of a service. Thelanguage may be specified according to a type of an XML data.

The atsc:capabilityCode may specify capability required to generatemeaningful presentation of content of a corresponding service by areceiver. In some embodiments, the present field may specify apredefined capability group. Here, the capability group may be a groupof values of capability attributes for meaningful presentation. In someembodiments, the present field may be omitted.

The deliveryMethod may be a container of transport related toinformation belonging to content of a service in a broadcast and(optionally) broadband mode of access. With regard to data contained inthe corresponding service, when the number of the data is N, deliverymethods for the respective data may be described by the element. ThedeliveryMethod element may include an atsc:broadcastAppService elementand an atsc:unicastAppService element. Lower elements may havebasePattern elements as lower elements, respectively.

The atsc:broadcastAppService may be DASH representation transmitted on amultiplexed or de-multiplexed type of broadcast including acorresponding media component belonging to a service over all timeperiods of contained media presentation. That is, each of the presentfields may refer to DASH representation transmitted through a broadcastnetwork.

The atsc:unicastAppService may be DASH representation transmitted on amultiplexed or de-multiplexed type of broadband including aconfiguration media content component belonging to a service over alltime periods of contained media presentation. That is, each of thepresent fields may refer to DASH representation transmitted through abroadband.

The basePattern may be a character pattern that is used by a receiverfor match with all portions of a segment URL used by a DASH client inorder to require media segment of parent representation in a containedperiod. The match may suggest that corresponding required media segmentis transmitted on broadcast transport. According to a URL address forreceiving DASH representation represented by each of theatsc:broadcastAppService element and the atsc:unicastAppService element,a portion of the URL may have a specific pattern and the pattern may bedescribed according to the present field. Data of a predeterminedportion can be segmented through the information. Proposed defaultvalues may be changed in some embodiments. The illustrated use columnsmay be related to respective fields, M may refer to a required field, Ois an optional field, OD may refer to an optional field having a defaultvalue, and CM may refer to a conditional required field. 0 . . . 1 to 0. . . N may refer to available numbers of corresponding fields,respectively.

FIG. 70 is a diagram illustrating S-TSID according to an embodiment ofthe present invention.

The S-TSID may be SLS XML fragment for providing overall sessiondescribed information about a transmission session for transmitting acontent component of a service. The S-TSID may be SLS metadata segmentincluding overall transmission session described information about aconfiguration LCT session and zero or more ROUTE sessions fortransmitting a media content component of a service. The S-TSID mayinclude file metadata about a delivery object or object flow transmittedin an LCT session of a service as well as additional information about acontent component transmitted in an LCT session and a payload format.

Each case of S-TSID fragments may be referenced in a USBD fragmentaccording to @atsc:sTSIDUri attribute of the userServiceDescriptionelement. The S-TSID may be represented in the form of a binary format orXML document.

The illustrated S-TSID may have an S-TSID root element. The S-TSID rootelement may include @serviceId, RS, and/or MS.

The @serviceID may be reference corresponding to a service element inLLS (FIT). A value of corresponding attribute may reference a servicehaving a corresponding value of the service_id in the FIT. Theinformation may be present when an MMTP session is used in order totransmit broadcast of a linear service that does not use a ROUTE sessionand does not use a USD.

The RS element may have information about a ROUTE session fortransmitting corresponding service data items. Since service data andservice components can be transmitted through a plurality of ROUTEsessions, the present element may have numbers of 1 to N.

The RS element may include @bsid, @sIpAddr, @dIpAddr, @dport, @PLPID,and/or LS.

The @bsid may be an identifier of a broadcast stream for transmitting acontent component of the broadcastAppService. When correspondingattribute is not present, a PLP of a default broadcast stream maytransmit an SLS fragment for a corresponding service. The value may bethe same as the broadcast_stream_id in the FIT (SLT).

The @sIpAddr may indicate a source IP address. Here, the source IPaddress may be a source IP address of a ROUTE session for transmitting aservice component included in a corresponding service. As describedabove, service components included in one service may be transmittedthrough a plurality of ROUTE session. Accordingly, the service componentmay be transmitted to other ROUTE sessions, but not to a ROUTE sessionfor transmitting the corresponding S-TSID. Accordingly, in order toindicate a source IP address of the ROUTE session, the present field maybe used. A default value of the present field may be a source IP addressof a current ROUTE session. When a service component transmitted throughother ROUTE sessions is present and thus the ROUTE session needs to beindicated, a value of the present field may be a source IP address valueof the ROUTE session. In this case, the present field may be M, that is,a required field.

The @dIpAddr may indicate a destination IP address. Here, thedestination IP address may be a destination IP address of a ROUTEsession for transmitting a service component included in a correspondingservice. For cases such as the case described with regard to the@sIpAddr, the present field may indicate a destination IP address of aROUTE session for transmitting a service component. A default value ofthe present invention may be a destination IP address of a current ROUTEsession. When a service component transmitted through other ROUTEsessions is present and thus the ROUTE session needs to be indicated, avalue of the present field may be a destination IP address of the ROUTEsession. In this case, the present field may be M, that is, a requiredfield.

The @dport may indicate a destination port. Here, the destination portmay be a destination port of a ROUTE session for transmitting a servicecomponent included in a corresponding service. For cases such as thecase described with regard to the @sIpAddr, the present field mayindicate a destination port of a ROUTE session for transmitting aservice component. A default value of the present field may be adestination port number of a current ROUTE session. When a servicecomponent transmitted through other ROUTE sessions is present and thusthe ROUTE session needs to be indicated, a value of the present fieldmay be a destination port number value of the ROUTE session. In thiscase, the present field may be M, that is, a required field.

The @PLPID may be an ID of a PLP for a ROUTE session represented by RS.A default value may be an ID of an LCT session included in a currentS-TSID. In some embodiments, the present field may have a value of an IDvalue of a PLP for an LCT session for transmitting the in acorresponding ROUTE session and may have ID values of all PLPs for acorresponding ROUTE session. Information such as the @PLPID may beincluded in signaling transmitted through a link layer and transmittedto a receiver.

The LS element may have information about an LCT session fortransmitting corresponding service data items. Since service data andservice components can be transmitted through a plurality of LCTsessions, the present element may have numbers of 1 to N.

The LS element may include @tsi, @PLPID, @bw, @startTime, @endTime,SrcFlow, and/or RprFlow.

The @tsi may indicate a TSI value of an LCT session for transmitting aservice component of a corresponding service.

The @PLPID may have ID information of a PLP for a corresponding LCTsession. The value may be overwritten by a basic ROUTE session value.

The @bw may indicate a maximum bandwidth value. The @startTime mayindicate a short time of a corresponding LCT session. The @endTime mayindicate an end time of a corresponding LCT session. The SrcFlow elementmay describe a source flow of ROUTE. The RprFlow element may describe arepair flow of ROUTE.

The proposed default values may be varied according to an embodiment.The “use” column illustrated in the figure relates to each field. Here,M may denote an essential field, O may denote an optional field, OD maydenote an optional field having a default value, and CM may denote aconditional essential field. 0 . . . 1 to 0 . . . N may indicate thenumber of available fields.

The MS element may include @versionNumber information, @bsidinformation, @sIpAddr information, @dIpAddr information, @dportinformation, @packetId information, @PLPID information, @bw information,@startTime information, and/or @endTime information.

The MS element may be an element including an MMTP session. Informationincluded in the MS element may be included in an MMT signaling messageand transmitted.

The @versionNumber information may be information indicating a versionnumber of an MMTP protocol used in an MMTP session.

The @bsid information may be information indicating an identifier of abroadcast stream for transmitting content components.

The @sIpAddr information may be information indicating a source IPaddress of a packet for transmitting a content component.

The @dIpAddr information may be information indicating a destination IPaddress of a packet for transmitting a content component.

The @dport information may be information indicating a destination portnumber of a packet for transmitting a content component.

The @packetId information may be information indicating an MMTP packetid for transmitting an MMT signaling message of the MMTP session.

The @PLPID information may be information for identifying a PLP for anMMTP session. The @PLPID information may be included in signalingtransmitted through a link layer.

The @bw information may be information indicating a maximum bandwidthfor an MMTP session.

The @startTime information may be information indicating a start time ofan MMTP session.

The @endTime information may be information indicating an end time of anMMTP session.

Hereinafter, media presentation description (MPD) for ROUTE/DASH will bedescribed.

The MPD may be a SLS metadata fragment (e.g., one TV program during apredetermined period or a combination of consecutive linear TV programs)including formulated description of DASH media presentationcorresponding to a linear service of duration determined by abroadcaster. Convent of the MPD may provide context of a resourceidentified in media presentation and a source identifier of a fragment.A data structure and semantics of MPD segment may be conformable to MPDdefined by the MPEG DASH.

One or more DASH representation transmitted from the MPD may betransmitted on broadcast. The MPD may describe additional representationtransmitted in a broadband like in a hybrid service or support servicecontinuity in handoff to broadcast from broadcast due to degradation(e.g., driving in a tunnel) of a broadcast signal.

FIG. 71 is a diagram illustratingATSC_physical_layer_pipe_identifier_descriptor( ) according to anembodiment of the present invention.

When MMTP sessions are used in order to transmit an ATSC3.0 streamingservice, an MMT signaling message may be transmitted by the MMPTaccording to a signaling message mode defined in the ISO/IEC 23008-1.Each MMTP session may transmit an MMT signaling message and componentsand packets for transmitting the MMT signaling may be signaled by an MSelement in an S-TSID fragment.

As defined in the ISO/IEC 23008-1, the MMT signaling message may includePA, MPI, MPT, and HRBM messages, and an MP table in the MMT signalingmessage may transmit asset location information for ATSC3.0 servicecomponents. In this case, the illustratedATSC_physical_layer_pipe_identifier_descriptor( ) may be transmitted asasset_descriptor( ) of an MP table. WhenATSC_physical_layer_pipe_identifier_descriptor(is not shown, an assetmay be t transmitted through the same PLP as a PLP indicated by theMS@PLPID information in the S-TSID fragment.

The ATSC_physical_layer_pipe_identifier_descriptor( ) may includedescriptor_tag information, descriptor_length information, and/or PLP_idinformation.

The descriptor_tag information may be information for identifying thedescriptor.

The descriptor_length information may be information that is included ina descriptor and indicates a size (size) of information items subsequentto the information.

The PLP_id information may be information indicating an identifier of aPLP including MMTP packets for an asset described by the descriptor.

FIG. 72 is a diagram illustrating a hierarchical signaling structure ofan ATSC3.0 system according to an embodiment of the present invention.

The drawing illustrates the case in which two S-TSID instances aretransmitted through ROUTE. A first S-TSID may provide access informationfor LCT sessions included in ROUTE session #1. The ROUTE session #1 maytransmit content components of service_X. A second S-TSID may provideaccess information for LCT sessions included in ROUTE session #N, andthe ROUTE session #N may transmit content components of service_Y.

A receiver may acquire LCT sessions for transmitting components forrespective services using information items included in theaforementioned S-TSID fragment.

Prior to the aforementioned procedure for acquiring a component of aservice, the receiver may scan services.

FIG. 73 is a diagram illustrating flow of a rapid channel scan operationaccording to an embodiment of the present invention.

According to an order of numbers illustrated in the drawing, the rapidchannel scan operation may be performed.

First, a tuner in a receiver may scan frequencies using a predefinedfrequency list.

Second, the tuner may be on standby to receive a signal for eachfrequency.

Third, upon detecting a signal from one frequency, a baseband processormay extract an FIT and transmit the FIT to a middleware module.

Fourth, the middleware module may transmit the FIT to a FIT parser.

Fifth, the FIT parser may parse data of the FIT to extract information.Even if FITs having the same version number is present in a receiver ina last scan procedure, re-performance of a parsing procedure may be amost excellent processing procedure in terms of stability. This isbecause a version number may exceed a maximum number to return to aninitial version number and an FIT that accidently has the same versionnumber as a previous FIT is frequently transmitted. In a scenario inwhich a FIT is not updated, the receiver may initialize a version numberof the FIT.

Sixth, information extracted from the FIT may be stored in a channel map(database or storage).

FIG. 74 is a diagram illustrating flow of an entire channel scanningoperation according to an embodiment of the present invention.

When a receiver performs entire scan on service signaling (USBD or USD)for each service, the receiver may store or acquire more abundantinformation. For example, a longer service name may be acquired from theUSD and may be matched with a service_id value in the USD and the FIT tostore the name as a name of a corresponding service in a channel map.

A procedure of entire scan of a service may be performed as followsaccording to an order of numbers illustrated in the drawing.

First, a tuner in a receiver may scan frequencies using a predefinedfrequency list.

Second, the tuner may be on standby to receive a signal for eachfrequency.

Third, upon detecting a signal from one frequency, a baseband processormay extract an FIT and transmit the FIT to a middleware module.

Fourth, the receiver may check whether a FIT_version is new or not. Evenif FITs having the same version number is present in a receiver in alast scan procedure, re-performance of a parsing procedure may be a mostexcellent processing procedure in terms of stability. This is because aversion number may exceed a maximum number to return to an initialversion number and an FIT that accidently has the same version number asa previous FIT is frequently transmitted. When the version is new, themiddleware module may collect FITs and transmit the FITs to an FITparser.

Fifth, the FIT parser may parse data of the FIT to extract information.Even if FITs having the same version number is present in a receiver ina last scan procedure, re-performance of a parsing procedure may be amost excellent processing procedure in terms of stability.

Sixth, information extracted from the FIT may be stored in a channel map(database or storage).

Seventh, the receiver may obtain SLS bootstrapping information from theFIT.

Eighth, the receiver may transmit SLS bootstrapping information to aROUTE client.

Ninth, the receiver may perform signaling filtering to obtain and storeUSD in order to the USD from the SLS.

Tenth, a signaling parser may parser the USD. Here, even if SLSs havingthe same version number is present in a receiver in a last scanprocedure, re-performance of a parsing procedure may be a most excellentprocessing procedure in terms of stability. This is because a versionnumber may exceed a maximum number to return to an initial versionnumber and a SLS that accidently has the same version number as aprevious SLS is frequently transmitted.

Eleventh, the receiver may perform mapping with a service_id and updatea channel map.

FIG. 75 is a diagram illustrating a procedure for acquiring a service inpure broadcast according to an embodiment of the present invention.

When video and audio segments are transmitted through a pure broadcasthaving one ROUTE session, service acquisition using service signalingmay be performed in the following order.

First, USD, S-TSID, and MPD may be acquired and parsed together. Alltables may be required for service acquisition.

Then, representation for presentation may be selected. In this case, theS-TSID needs to be checked in order to determine representations to betransmitted through a broadcast network.

Then, the receiver may transmit information to a segment acquisitionmodule for providing user preference using corresponding signaling fromsignaling (USD, S-TSID, and MPD). For example, a user may prefer Spanishaudio to English audio. In this case, information related to userpreference may be stored in the receiver, and a component of a serviceprovided in Spanish preferred by the user may be selected using theinformation and information related to an audio language in the USD, theS-TSID, and/or MPD.

Then, the segment acquisition module may determine a componenttransmitted through a broadcast stream using information described inthe USD. The segment acquisition module may acquire information aboutwhere the component is acquired, using the USD. When a DASH clientrequest one segment from an internal proxy server, the internal proxyserver needs to know whether the internal proxy server requests acorresponding segment from a remote broadband server or (when there isno corresponding segment) the internal proxy server is on standby untilthe corresponding segment appears in a broadcast stream. The USD maydescribe multicast “base patterns” and unicast “base patterns” in adeliveryMethod element. The proxy server may check whether the unicastbase patterns or the multicast base patterns are substring to a URLprovided by a DASH player and may be operated according to the result.

Then, in the case of pure broadcast, the receiver may know a place inwhich components can be acquired without any deliveryMethod element inthe USD.

FIG. 76 is a diagram illustrating a procedure for acquiring a servicethrough a plurality of ROUTE sessions in pure broadcast according to anembodiment of the present invention.

The plurality of ROUTE sessions may be used to transmit data orcomponents included in one service. In this case, the S-TSID may includeadditional ROUTE session information required to access allrepresentations by a receiver.

Referring to the drawing, the receiver may receive a FIT and acquire anSLS for a specific service. The receiver may acquire the S-TSID forproviding information about an allocated ROUTE session/LCT session of acorresponding service with reference to information of the USD in theacquired SLS. The S-TSID may indicate that components of service #1 aretransmitted by ROUTE session #1 and ROUTE session #2. The receiver mayrefer to information about ROUTE session #2 as well as information aboutROUTE session #1 to be contained in the S-TSID in order to acquirecomponents of service #1.

FIG. 77 is a diagram illustrating a procedure for bootstrappingelectronic service guide (ESG) through a broadband network according toan embodiment of the present invention.

Bootstrapping of the ESG may be signaled through a broadband. Referringto the embodiment, all ESG data may be transmitted through a broadband.Accordingly, ESG broadcast bootstrapping information in the FIT may bereplaced by ESG broadband bootstrapping information. For example, aURL_type of the inet_signaling_location_descriptor( ) may indicatewhether a type of a URL is an ESG or not.

Referring to the drawing, the receiver may previously acquire the FITand may parse the inet_signaling_location_descriptor( ) in the FIT. Asdescribed above, the inet_signaling_location_descriptor( ) may provide aURL of a server for providing the ESG and the receiver may access theURL to acquire ESG data through a broadband.

FIG. 78 is a diagram illustrating a procedure for acquiring a servicethrough broadcast and broadband according to an embodiment of thepresent invention.

When two or more audio components with different languages aretransmitted through different paths, one component may be transmittedthrough a broadband network and the other one component may betransmitted through a broadband network. In this case, the S-TSID mayinclude information for describing all broadband components such that aROUTE client acquires desired components. In addition, when a DASHclient issues request for a segment, the USD may include URL patternsfor a broadcast network and URL patterns for a broadband network suchthat a receiver middleware describes segments to be transmitted and apath through the segments are transmitted. In this case, the middlewaremay know a segment to be requested from a remote broadband server and asegment to be searched for from a broadcast network.

Referring to the drawing, the receiver may acquire the FIT from abroadcast signal and receive an SLS for a specific service usinginformation in the FIT. The receiver may know that each component istransmitted through a broadcast network and a broadcast network for acorresponding service using information in the USD (or USBD) in the SLS.For example, an English audio component for a corresponding service maybe transmitted through a broadcast network and a Spanish audio componentmay be transmitted through a broadband network. The USD may include basepattern information used to acquire an English audio componenttransmitted through a broadcast network and may also include basepattern information used to acquire a Spanish audio componenttransmitted through a broadband network. The English audio component maybe acquired using information in the USD and information in the S-TSID,and the Spanish audio component may be acquired using information in theUSD from an external server. The receiver may perform a switchingoperation between the English audio component and the Spanish audiocomponent using the information of the MPD.

FIG. 79 is a diagram illustrating signaling for an operation forchanging reception of a service between broadcast and a broadbandaccording to an embodiment of the present invention.

The receiver may change reception to a broadband network from abroadcast network or to a broadcast network from a broadband network.The receiver may use signaling information included in the USD in thisprocedure. The USD may include information about components to betransmitted through a broadcast network or a broadband network. Ifpossible, the receiver middleware may receive through a broadcastnetwork or there is a problem in reception through a broadcast network,a component may be acquired through a broadband network.

Referring to the drawing, the receiver may parse an FIT and an SLS andparse USD in the SLS. The USD may indicate that a video component and anaudio component included in a service are transmitted through abroadcast network and a broadband network and may include base patterninformation required to receive a corresponding component in each of abroadcast network and a broadband network. The receiver may acquire acomponent through any one path according to the quality of a broadcastnetwork or broadband network connected to the receiver using informationin the USD. Change between components that are transmitted through thebroadcast network and the broadband network, respectively, may beperformed using information in the MPD by the receiver.

FIG. 80 is a diagram illustrating signaling of receiver capabilityinformation according to an embodiment of the present invention.

As described above, some or all fragments of SLS may include informationindicating capability of a receiver, which is required to significantlypresent a specific service or components.

According to the embodiment of the present invention, a scalable codingscheme needs to be applied to a service or a component and a receiverneeds to process the data to which the scalable coding is applied.

First, in the embodiment of the present invention, the USD may includeinformation about required capability in order to render a service. Forexample, video resolution may be required capability to decode video. Tothis end, the USD may have capability such as ‘HD” or “UHD”. This mayindicate that a current service or program is provided in the form of HDor UHD. In addition, the USD may include information indicatingcapability for processing other components such as audio, closedcaption, or an available application.

Then, the receiver may know a component for rendering a UHD service or aHD service using information in the MPD. That is, referring to thedrawing, @dependencyId in the MPD may include information foridentifying representation that is dependent upon representation ofvideo. The receiver may provide HD video using basic videorepresentation (Rv) and provide UHD video additionally using enhancedvideo representation (Rev).

FIG. 81 is a diagramming illustrating the meaning of a LCT transportobject identifier (TOI) field and information included in the field forfiltering of a fragment according to an embodiment of the presentinvention.

In order to rapidly filter signaling fragment using a receiver as atarget, the LCT TOI field may be classified into three parts.

A first part may be a fragment type part and may be allocated to the TOIfield in order to identify a type of signaling fragment.

A second part may be a fragment type extension part and may be allocatedto the TOI field in order to identify a sub type of a fragment.According to an embodiment for allocating a sub type, when a pluralityof fragments is transmitted, a type of a fragment of a bit map formatincluded in an object may be identified in order to filter a separatefragment. According to another embodiment for allocating a sub type,when a plurality of instances of a signaling fragment having the samefragment type (e.g., when a plurality of MPDs are present in a boundarybetween programs), an identifier for an instance may be indicated.

A third part may be a version part and may be allocated to the TOI fieldin order to indicate a version of an object identified by the fragmenttype extension part and the fragment type part.

An LCT TOI field according to the present embodiment may be classifiedinto a fragment type part, a fragment type extension part, and/or aversion part.

The fragment type part may include a value for identifying a type ofservice layer signaling for transmitting a current object. For example,when a value of a fragment type part is ‘0x00’, the value may indicatethat a bundle of the SLS is transmitted through the object, when a valueof the fragment type part is ‘0x01’, the value may indicate thatUSBD/USD of the SLS is transmitted through the object, when a value ofthe fragment type part is ‘0x02’, the value may indicate that the S-TSIDof the SLS is transmitted through the object, and when a value of thefragment type part is ‘0x03’, the value may indicate that the MPD of theSLS is transmitted through the object.

When the object includes a plurality of fragments, the fragment typeextension part may be a bitmap indicating a fragment to be contained.When the object includes one fragment, values for identifying a sub typeof a service signaling fragment for more detailed filtering may beallocated to this part. Referring to the drawing, when a fragment typepart indicates that a bundle of SLSs is transmitted through one object,whether a specific fragment corresponds to USBD/USD, S-TSID, or MPDaccording to a value of a fragment type extension type. When thefragment type part identifies a signaling fragment included in oneobject (when a value of the fragment type part is ‘0x01’ to ‘0x03’), thefragment type extension part may have a hashed value of 16 bits,extracted from a URL of the service layer signaling fragment, the partmay be used to filter a fragment having an instance URL before a clientassembles an LCT packet.

A version part may indicate a version number of an entire object. Whenthe object includes one fragment, the part may include a version numberof a corresponding fragment. When the object includes combinations offragments, the part may include a version number for an object andaccordingly, the case in which a fragment included in the object ischanged may be identified. The version number of the object may beincreased on 1-by-1 basis whenever a fragment in the object is changed.

When a value of the TOI is 0 or 1, the TOI may be reserved fortransmission of the EFDT, and in this case, information of the TOI fieldmay not be used to filter the EFDT. An LCT code point may be identifiedfor a payload type, and a receiver may use the field in order todetermine a type of a payload transmitted through an LCT session insteadof the TOI value.

FIG. 82 is a diagram illustrating MetadataEnvelope of XML form forapplying template-based compression to signaling according to anembodiment of the present invention.

XML signaling fragments described in the present invention may becompressed using a compression tool such as Gzip but may be compressedusing a Diff and Path tool via another method. In a Diff and Patchprocedure, an XML signaling template may be pre-shared between a senderand a receiver. The procedure may include comparing two XML files, XMLsignaling template and XML signaling instance and generating outputindicating a difference, which is referred to as Diff, between the twoXML files by a sender side.

Here, the signaling template may be used by a term indicating a basicstructure of a signaling fragment.

Here, the signaling instance may correspond to the aforementionedsignaling fragment and may be used as a term indicating signalingfragment including information for a feature service, content, and soon. For example, when the S-TSID is signaling fragment defined for oneservice, S-TSID fragment transmitted for a specific service may bereferred to as an S-TSID instance.

Diff may be encapsulated as a metadata envelope element like a generalXML signaling instance. When Diff is generated at the sender side, theDiff may be encapsulated in content of an update element and then may beencapsulated in the metadata envelope. The metadata envelope may betransmitted to a plurality of receivers through a signaling channel. Thereceiver may receive and check the metadata envelope and check whetherthe metadata envelope element include a diffUpdate element. When thediffUpdate element is included in the metadata envelope element, thereceiver may recognize that the diffUpdate element needs to be processedin a compression mode.

The receiver may optionally search for a signaling template ofmetadataURI attribute (SignalingTemplate ID) together with versionattribute (SignalingTemplateVersion) from the pre-shared and storedsignaling templates. When the corresponding signaling template cannot bediscovered, the receiver may attempt to acquire a signaling templatehaving a URL of the SignalingTemplate ID via a GET procedure.

The receiver may apply the transmitted Diff to the acquired signalingtemplate to recover a signaling instance. The signaling fragment mayhave a pair of version attribute (SignalingInstanceVersion) andmetadataURI attribute (SignalingInstanceID). It may be required totransmit only the difference (e.g., an element or added attribute valueand changed or deleted content) as an updated portion of a templaterather than to transmit a complete file. The receiver may apply thedifference to the signaling template to acquire signaling fragments(patch procedure). When the acquired fragment is compared with anoriginal complete fragment and a fragment with a very small differenceneeds to be transmitted, if compression is performed using a Diff andPatch procedure instead of a conventional compression method, very highefficiency may be achieved for transmission and processing of data.

As described with regard to the 3GPP-MBMS, the metadata envelope and themetadata fragment may be compressed using Gzip. When there is noupdating target at a server side, a diff message without Diff may betransmitted to a client such that a client generates a signalingfragment at a position in which instantiation of a signaling fragment isrequired. The diff message without Diff may be frequently transmittedand accordingly, the receiver may periodically check signalingfragments.

Diff may be defined in the form of XML and may include content about achanged portion of information and/or an element of the aforementionedsignaling fragment. The metadata envelope including Diff may includeinformation for identifying a signaling fragment to which correspondingDiff needs to be applied and/or information indicating a version of asignaling fragment to which the corresponding Diff is applied. Areceiver may check a signaling fragment to which Diff is applied usinginformation for identifying a signaling fragment from the metadataenvelope and check whether Diff needs to be applied using informationindicating a version of signaling fragment to which Diff is applied.When versions are different, the receiver may apply content of Diff to acorresponding signaling fragment to update and store the correspondingsignaling fragment.

FIG. 83 is a diagram illustrating a compression procedure of atemplate-based signaling fragment according to an embodiment of thepresent invention.

The signaling template fragment may be identified by a URL included incontent of the template ID element. The template per se may be fetchedand pre-shared through HTTP(s) via a broadband. Upon first obtaining adiff message, the receiver may store the diff message for future use.The template may correspond to a fragment at a specific time point, andthe signaling fragment may be generated using a method applied in orderto generate an instance to which a subsequent diff message issubsequent. In this case, information for identifying a mode in which afixed template is used or a mode in which a template is provided as afragment instance may be included in the signaling.

Referring to the drawing, a sender side may generate signaling andgenerate a signaling instance (the aforementioned signaling fragment). Asender may compare the generated signaling instance with apre-transmitted (or pre-stored) signaling instance to generate a diffmessage including Diff. In a procedure for generating the diff message,the signaling template may be used. The sender may transmit thegenerated diff message to a receiver side.

The receiver side may receive the diff message and apply Diff includedin the corresponding diff message to the signaling template to completea signaling instance. As described above, according to a mode, thesignaling template may be pre-shared or a signaling fragment that thereceiver first receives may be used as a template. The receiver side mayacquire the aforementioned signaling fragment using the completedsignaling instance, according to the present invention. The receiverside may acquire a service using the acquired signaling fragments, asdescribed above.

FIG. 84 is a diagram illustratingbroadcast_signaling_location_descriptor( ) according to anotherembodiment of the present invention.

As described above, the broadcast_signaling_location_descriptor( ) mayinclude information about a bootstrap address for service layersignaling. A receiver may acquire an SLS transmitted for each serviceusing the information about the bootstrap address.

According to another embodiment of the present invention, thebroadcast_signaling_location_descriptor( ) may include descriptor_taginformation, descriptor_length information, SLS_protocol typeinformation, IP_version_flag information, SLS_source_IP_address_flaginformation, SLS_source_IP_address information,SLS_destination_IP_address information, SLS_destination_UDP_portinformation, SLS_TSI information, SLS_packet_id_flag information,version_number_flag information, start_time_flag information,end_time_flag information, SLS_packet_id information, version_numberinformation, start_time information, end_time information, bandwidthinformation, and/or SLS_PLP_ID information.

The SLS_protocol_type information may be information indicating a tyhpeof a protocol of a channel for transmitting service layer signalingdefined at an upper level of UDP/IP. For example, when a value allocatedto the SLS_protocol_type information is ‘0x00’, the value may indicatethat a type of a protocol used to transmit service layer signaling isnot identified, when a value allocated to the SLS_protocol_typeinformation is ‘0x01’, the value may indicate that a type of a protocolused to transmit service layer signaling is ROUTE, and a value allocatedto the SLS_protocol_type information is ‘0x02’, the value may indicatethat a protocol used to transmit service layer signaling is MMT.

The SLS_source_IP_address information may be information indicating asource IP address of an LCT or MMTP channel for transmitting servicelayer signaling.

The SLS_destination_IP_address information may be information indicatinga destination IP address of an LCT or MMTP channel for transmittingservice layer signaling.

The SLS_destination_UDP_port information may be information indicating aUDP port number of an LCT or MMTP channel for transmitting service layersignaling.

The SLS_packet id flag information may be information for identifyingwhether SLS_packet_id information is present.

The version_number_flag information may be information for identifyingwhether version_number information is present.

The start_time_flag information may be information for identifyingwhether start_time information is present.

The end_time_flag information may be information for identifying whetherend_time information is present.

The SLS_packet_id information may be information for identifying apacket of an MMTP channel for transmitting service layer signaling for aservice.

The version_number information may be information of a version number ofan MMTP used in an MMTP session including an MMTP channel fortransmitting service layer signaling.

The start_time information may be information indicating start time ofan MMTP session including an MMTP channel of service layer signaling fora service.

The end_time information may be information indicating end time of anMMTP session including an MMTP channel of service layer signaling for aservice.

The bandwidth information may be information for identifying a bandwidthallocated for an MMTP session. The bandwidth_flag information may befurther included in the descriptor or an SLT and may identify whetherthe bandwidth information is present.

Details of other information items to be added to thebroadcast_signaling_location_descriptor( ) may be substituted withdescription of information items having the same titles as the abovedescription.

FIG. 85 illustrates a method of providing a broadcast service(transmitting side) according to an embodiment of the present invention.

The method of providing a broadcast service (transmitting side)according to an embodiment of the present invention can includegenerating streaming components of the broadcast service, generating NRT(Non-Real Time) components of the broadcast service, generating a SLS(Service Layer Signaling), processing into MMT packets based on the MMTprotocol, processing into ROUTE packets based on the ROUTE protocol,generating a SLT (Service List Table), processing the SLT/the MMTpackets/the ROUTE packets into broadcast signals and/or transmitting thebroadcast signals.

First, the first service module of the transmitting side may generatestreaming components of a broadcast service. Here, the streamingcomponent may mean the linear service component, audio/video servicecomponent, etc. of the broadcast service. Here, the streaming componentsincluded in the broadcast service may be generated in a data format suchas MPU based on MPEG media transport (MMT) protocol. Here, the firstservice module may be a hardware block for generating service data basedon the MMT protocol.

The second service module may generate NRT components of theabove-described broadcast service. The NRT component may be referred toas a locally cached file, a locally cached content item, etc. accordingto the embodiment. The NRT components may be generated in a format suchas a DASH media segment based on ROUTE protocol and may be transmittedbased on the ROUTE protocol. The NRT components may include data used toprovide app-based enhancement for the above-described broadcast service.As described above, application based supplementary information(enhancement) may be provided to the broadcast service (or the linearservice of the broadcast service). Data, content items and filesnecessary therefor may be delivered to the receiver using the NRTmethod. According to the embodiment, such data may be transmitted viabroadband. The second service module may be a hardware block forgenerating service data based on the ROUTE protocol.

The third service module may generate an SLS for signaling the broadcastservice. Here, the SLS may be delivered based on the MMT protocol. TheSLS was described above. The third service module may be a hardwareblock for generating and managing the SLS for the broadcast service.

The first transport processor may process the above-described streamingcomponents and/or the above-described SLS into MMP packets based on theMMT protocol. That is, in the present embodiment, the MMT protocol maybe used to deliver streaming data. The first transport processor may bea hardware block for generating the MMTP packets based on the MMTprotocol.

The second transport processor may process the above-described NRTcomponents into ROUTE packets based on the ROUTE protocol. As describedabove, when service data is delivered in NRT, the service data may bedelivered based on the ROUTE protocol. The second transport processormay be a hardware block for generating ROUTE packets based on the ROUTEprotocol.

The fourth service module may generate the above-described SLT. Asdescribed above, the SLT may include bootstrap information. In thepresent embodiment, the bootstrap information may indicate an MMTPsession for delivering the above-described SLS. The bootstrapinformation may indicate a transport session using IP/UDP information.The bootstrap information may include the IP address, UDP port number,etc. of the MMTP session. The fourth service module may be a hardwareblock for generating and managing the SLT for the broadcast service.

The third transport processor may process the above-described SLT, MMTpackets and/or ROUTE packets into the broadcast signal. In this process,the third transport processor may perform UDP/IP processing with respectto data and encapsulate the data into IP packets. In addition, after theIP packets are processed into link layer packets, a broadcast signal maybe generated via physical processing. Here, the FIC is not used and theSLT is encapsulated into IP packets and is delivered based on a PLP.Link layer processing and physical processing were described above. Thethird transport processor may be divided into a plurality of detailedmodules for managing layers. The transmission unit of the transmittingside may transmit a broadcast signal. This transmission unit may be anantenna, etc.

In a method of providing a broadcast service (transmitting side)according to other embodiment of the present invention, the SLS caninclude information providing component acquisition information for thestreaming components and/or the NRT components. This information mayinclude a USBD and/or MP table as described above.

In a method of providing a broadcast service (transmitting side)according to another embodiment of the present invention, the SLS canfurther include an AST (Application Signaling Table) that signals theapp-based enhancement. The AST was described above.

In a method of providing a broadcast service (transmitting side)according to another embodiment of the present invention, the AST caninclude at least one application elements providing information aboutapplications of the app-based enhancement. Each of the applicationelements can include content item elements providing information aboutthe content items of the app-based enhancement. These content itemelements may describe information on content item for theabove-described app-based enhancement delivered in NRT.

In a method of providing a broadcast service (transmitting side)according to another embodiment of the present invention, the contentitem elements can include linkage information linking the content itemsand file delivery description. Here, the file delivery descriptioncorresponds to EFDT described above. EFDT can describe informationrelated to file delivery, and can be delivered by S-TSID describedabove.

In a method of providing a broadcast service (transmitting side)according to another embodiment of the present invention, the SLT canfurther include URL information for an event table delivering events.The events, as notifications initiating actions to be taken by theapplications, are the same as described above. Through this URLinformation, the receiver may acquire an event table. Here, the eventtable may correspond to the above-described EMT or AEI. In the presentembodiment, the event table may be the AEI.

In a method of providing a broadcast service (transmitting side)according to another embodiment of the present invention, the eventtable can include plural event elements and an identifier for a timereference. The event elements can include data for the events and/ortime information. The time information can indicate presentation timefor the events relative to aforementioned time reference. Here, theidentifier for the time reference may be a DASH period, representationor a MPU, which is a criterion of the event time. In the presentembodiment, an event time may be indicated using the identified MPU asthe time reference.

In a method of providing a broadcast service (transmitting side)according to another embodiment of the present invention, theinformation in the SLS includes an USBD and/or a MMT table. Here, theMMT table may correspond to the above-described MP table or MMT table.The MMT table may provide a transport session description for MMTPsessions for delivering the above-described streaming components.Streaming components may be acquired using the information on the MMTtable. The USBD may include a reference for the above-described MMTtable and/or a reference for the above-described S-TSID. Other signalinginformation may be acquired via the USBD. The S-TSID may provide atransport session description for ROUTE sessions for delivering theabove-described NRT components. In this case, the S-TSID may bedelivered based on the MMT protocol. Even when streaming data istransmitted via the MMPT, NRT components may be acquired using theS-TSID.

A description will be given of a method of providing a broadcast service(receiving side) according to an embodiment of the present invention.This method is not illustrated in the figure.

The method of providing a broadcast service (receiving side) accordingto the embodiment of the present invention may include a reception unitof a receiving side receiving a broadcast signal, a first receptionprocessor of the receiving side parsing the broadcast signal to acquirean SLT, a second reception processor accessing an MMTP session fordelivering an SLS using bootstrap information of the SLT to acquire theSLS, a third reception processor acquiring streaming components of aspecific broadcast service using the SLS and/or a fourth receptionprocessor acquiring NRT components of the broadcast service using theSLS. Here, the streaming components may be transmitted via the MMTPsession based on the MMT protocol and the NRT components may betransmitted via the ROUTE session based on the ROUTE protocol. Thestreaming components and the SLS may be received in the form of the MMTPpackets and the NRT components may be received in the form of ROUTEpackets. The NRT components may include content items for app-basedenhancement related to the broadcast service.

The methods of providing the broadcast service (receiving side)according to the embodiments of the present invention may correspond tothe above-described methods of providing the broadcast service(transmitting side) according to the embodiments of the presentinvention. The methods of providing the broadcast service (receivingside) may be performed by hardware modules corresponding to the modulesused in the methods of providing the broadcast service (transmittingside) (for example, the first, second, third, fourth service module, thefirst, second, third transport processor, transmission unit, etc.). Themethod of providing the broadcast service (receiving side) may haveembodiments corresponding to the embodiments of the method of providingthe broadcast service (transmitting side) described above.

The above-described steps may be omitted or replaced by other steps forperforming the same/similar operations according to embodiment.

FIG. 86 is a diagram illustrating an apparatus for providing a broadcastservice (transmitting side) according to an embodiment of the presentinvention.

The apparatus for providing the broadcast service (transmitting side)according to the embodiment of the present invention may include thefirst, second, third, fourth service module, the first, second, thirdtransport processor and/or transmission unit described above. Therespective blocks/modules have been described above.

The apparatus for providing the broadcast service (transmitting side)according to the embodiment of the present invention and the internalblocks/modules thereof may perform the above-described embodiments ofthe method of providing the broadcast service (transmitting side) of thepresent invention.

A description will be given of an apparatus for providing a broadcastservice (receiving side) according to an embodiment of the presentinvention. This apparatus is not illustrated in the figure.

The apparatus for providing the broadcast service (receiving side)according to the embodiment of the present invention may include thereceiving unit, the first, second third and/or fourth receivingprocessor described above. The respective blocks/modules have beendescribed above.

The apparatus for providing the broadcast service (receiving side)according to the embodiment of the present invention and the internalblocks/modules thereof may perform the above-described embodiments ofthe method of providing the broadcast service (receiving side) of thepresent invention.

The above-described blocks/modules, etc. inside the apparatus maycorrespond to processors that execute continuous processes stored in amemory or hardware elements positioned inside/outside the apparatusaccording to embodiment.

The above-described modules may be omitted or replaced by other modulesfor performing the same/similar operations according to embodiment.

Modules or units may correspond to processors that execute continuousprocesses stored in a memory (or a storage unit). The respective stepsdescribed in the above-described embodiments may be performed byhardware/processors. The respective modules/blocks/units described inthe above embodiments may operate as hardware/processors. In addition,the methods proposed in the present invention may be executed as codes.These codes may be written in a processor-readable storage medium, andthus may be read by a processor provided by an apparatus.

Even though the respective drawings have been separately described forconvenience of description, embodiments described in the respectivedrawings may be merged into a new embodiment. In addition, designing ofa computer-readable recording medium in which a program for executingthe above-described embodiments according to necessity of a personskilled in the art is within the scope of the present invention.

Referring to the apparatuses and methods according to the presentinvention, configurations and methods of the embodiments are notrestrictively applicable, and all or some of the above-describedembodiments may be selectively combined and configured such that theembodiments can be variously changed

Meanwhile, the methods proposed in the present invention may beimplemented as processor-readable code stored in a processor-readablerecording medium included in a network device. The processor-readablerecording medium includes all types of recording devices in whichprocessor-readable data is stored. Examples of the processor-readablerecording medium include a ROM, a RAM, a CD-ROM, a magnetic tape, afloppy disk, an optical data storage device, etc. In addition, theexamples include a carrier-wave type implementation such as atransmission over the Internet. Furthermore, as the processor-readablerecording medium is distributed to a computer system connected via anetwork, processor-readable code can be saved and executed in adistributed manner.

Further, even though preferred embodiments of the present invention havebeen illustrated and described, the present invention is not restrictedto a certain embodiment described above, and various modifications andvariations can be made by those skilled in the art without departingfrom the subject matter of the present invention as defined by theclaims. Furthermore, these modified embodiments should not be understoodseparately from the spirit or scope of the present invention.

Both apparatus and method inventions are mentioned in this specificationand descriptions of both the apparatus and method inventions may becomplementarily applicable to each other.

It should be understood by those skilled in the art that various changesand modifications can be made in the present invention within the spiritor scope of the present invention. Therefore, the present invention isintended to include changes and modifications of the present inventionwithin the scope of accompanying claims and equivalents thereof.

Both apparatus and method inventions are mentioned in this specificationand descriptions of both the apparatus and method inventions may becomplementarily applicable to each other.

Various embodiments have been described in best modes.

The present invention is used in a series of broadcast signal provisionfields.

It is clear to those skilled in the art that various changes andmodifications can be made in the present invention within the spirit orscope of the present invention. Therefore, the present invention isintended to include changes and modifications of the present inventionwithin the scope of accompanying claims and equivalents thereof.

What is claimed is:
 1. A method of receiving broadcast signals, themethod comprising: receiving the broadcast signals; decoding a servicelayer table including bootstrap information from the received broadcastsignals, wherein the bootstrap information indicates an MPEG MediaTransport Protocol (MMTP) session carrying service layer signaling;decoding the service layer signaling from MPEG Media Transport (MMT)packets based on the MMTP and decoding a transport session descriptionfrom a ROUTE (Real-Time Object Delivery over Unidirectional Transport)session, wherein service components are delivered by the MMT packetsbased on MPEG Media Transport Protocol and wherein non-real timecomponents are delivered by Layered Coding Transport (LCT) packets inthe ROUTE session; and decoding the service components delivered in theMMT packets and the non-real time components delivered in the LCTpackets, respectively.
 2. The method of claim 1, wherein the servicelayer signaling includes an application signaling table that signalsapp-based enhancement.
 3. The method of claim 2, wherein the applicationsignaling table includes at least one application elements providinginformation about applications of the app-based enhancement.
 4. Themethod of claim 1 wherein the service layer signaling includes an UserService Bundle Description (USBD) and a MMT table, wherein the MMT tableprovides a transport session description for a MMTP session carrying theservice components, wherein the USBD includes a reference to the MMTtable and a reference to Service-based Transport Session InstanceDescription (S-TSID), and wherein the S-TSID provides the transportsession description for a ROUTE session carrying the non-real timecomponents.
 5. An apparatus for receiving broadcast signals, theapparatus comprising: a receiver configured to receive the broadcastsignals; a first decoder configured to decode a service layer tableincluding bootstrap information from the received broadcast signals,wherein the bootstrap information indicates an MPEG Media TransportProtocol (MMTP) session carrying service layer signaling; a seconddecoder configured to decode the service layer signaling from MPEG MediaTransport (MMT) packets based on the MMTP and decoding a transportsession description from a Real-Time Object Delivery over UnidirectionalTransport (ROUTE) session, wherein service components are delivered bythe MMT packets based on MPEG Media Transport Protocol and whereinnon-real time components are delivered by Layered Coding Transport (LCT)packets in the ROUTE session; and a component decoder configured todecode the service components delivered in the MMT packets and thenon-real time components delivered in the LCT packets, respectively. 6.A method of transmitting broadcast signals, the method comprising:generating service components and non-real time components of abroadcast service, wherein the service components are to be delivered byMPEG Media Transport (MMT) packets based on MPEG Media TransportProtocol (MMTP) and the non-real time components are to be delivered byLayered Coding Transport (LCT) packets in a Real-Time Object Deliveryover Unidirectional Transport (ROUTE) session, respectively; generatingservice layer signaling to be delivered the MMT packets based on theMMTP and generating a transport session description to be delivered theROUTE session; generating a service layer table including bootstrapinformation, wherein the bootstrap information indicates a MPEG MediaTransport Protocol (MMTP) session carrying the service layer signaling;and transmitting the broadcast signals carrying the MMT packets, the LCTpackets and the service layer table.
 7. The method of claim 6, whereinthe service layer signaling includes an application signaling table thatsignals app-based enhancement.
 8. The method of claim 7, wherein theapplication signaling table includes at least one application elementsproviding information about applications of the app-based enhancement.9. The method of claim 6, wherein the service layer signaling includesan User Service Bundle Description (USBD) and a MMT table, wherein theMMT table provides a transport session description for MMTP sessioncarrying the service components, wherein the USBD includes a referenceto the MMT table and a reference to Service-based Transport SessionInstance Description (S-TSID), and wherein the S-TSID provides thetransport session description for a ROUTE session carrying the non-realtime components.
 10. An apparatus for transmitting broadcast signals,the apparatus comprising: a component processor configured to generateservice components and non-real time components of a broadcast service,wherein the service components are to be delivered by MPEG MediaTransport (MMT) packets based on MPEG Media Transport Protocol (MMTP)and the non-real time components are to be delivered by Layered CodingTransport (LCT) packets in a Real-Time Object Delivery overUnidirectional Transport (ROUTE) session, respectively; a first signalprocessor configured to generate service layer signaling to be deliveredthe MMT packets based on the MMTP and generate a transport sessiondescription to be delivered the ROUTE session; a second signal processorconfigured to generate a service layer table including bootstrapinformation, wherein the bootstrap information indicates a MPEG MediaTransport Protocol (MMTP) session carrying the service layer signaling;and a transmitter configured to transmit the broadcast signals carryingthe MMT packets, the LCT packets and the service layer table.